What is the problem?

bool ActorManager::AddActorHandle(std::unique_ptr<ActorHandle> actor_handle,
                                  bool is_owner_handle, const TaskID &caller_id,
                                  const std::string &call_site,
                                  const rpc::Addres

Trying to --appimage-extract-and-run a x86_64 Linux AppImage on FreeBSD 12.1-RELEASE-p8 with the Linux compatibility layer:

user@FreeBSD$  /home/user/Downloads/Akira-26-x86_64.AppImage --appimage-extract-and-run
mkdir_p error: Permission denied
Failed to extract AppImage

but

user@FreeBSD$  /home/user/Downloads/Akira-26-x86_64.AppImage --appimage-extract

hi there,

Just installed latest versions of shipit packages and here's something new:

Running 'deploy:fetch' task...
Create workspace...
Workspace created: "/var/folders/s0/scv46d414cd28hyzsd5_pcrw0000gn/T/tmp-72206PXTF2WKB77Ro"
Initialize local repository in "/var/folders/s0/scv46d414cd28hyzsd5_pcrw0000gn/T/tmp-72206PXTF2WKB77Ro"
Running "git init" on local.
@ Initialized empty Gi

We are using font-awesome V4 and should migrate to font-awesome V5 which comes with its own vue.js module: https://github.com/FortAwesome/vue-fontawesome

Migration includes removing old font-awesome V4 module and changing all existing icons to new vue.js tag.

This is blocked until #114 is merged which comes with first initial integration.

SUMMARY

I just faced an embarrassed problem that command st2 action list keeps return 503.

I tried st2 --debug action list and the result in line HTTP_PROXY(uppercase) was empty. This mislead me that the proxy info was set(which is not).

I finally found that the root cause is a lowercase http_proxy env variable was set in the system.

So I think it maybe more friend

Currently Swagger OpenAPI spec does not refrence jsonData, so we should update the spec to reflect this