@richardliaw could we take in the data path as a command line arg for all these examples that defaults to "~/data"? That way the user can specify their own data paths without having to modify the code.

Originally posted by @amogkam in ray-project/ray#15260 (comment)

Command: cortex debug exec API_NAME

Behavior: choose a running API pod (at random is ok if there are multiple), and run e.g. kubectl exec -it api-iris-classifier-6d866654f8-pwz62 --container api -- /bin/bash

This command should be executed in the manager container, similar to how the cortex cluster up command works. However unlike cortex cluster up, this command will require interact

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

For SC Operator it may be a good idea to generate CRD manifests from inside a docker container.
This should provide reproducible generation step and avoid "produces different output on my machine" issues.

Linter should also fail if generation of manifests produce diff with the commited version.

To effectively introduce more useful features and fix old stuff, it is necessary to have more unit tests and increase our test coverage. At the moment we have ~28 % code coverage according to Codecov.
Furthermore some of our currently implemented tests are too rudimentary and have to be improved dramatically.

Related i

(suggested by Berndinox in #205; been bugging me for a while too)

Currently, the Docker image exposes port 80. We should change this so that running Meli doesn't require root access.

We'll need to update the deployment docs.