Search before asking

• I had searched in the issues and found no similar feature requirement.

Description

I want Ray Serve to throw the exception inside the deployment initialization. Currently, when there is an exeption inside the deployment's initialization stage, Ray only logs the exception, retries for 3 times, then throws the

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

Apart from Unit and Integration tests, we should also run the st2-self-check script for every PR as part of the CI pipeline.
Something we do in e2e and manual testing.

It should be possible with the Github Actions and would help us to catch bugs before merging into master.
Ex #5489.

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.

The documentation for creating complex inference graphs should include what components can be connected to what, and how the overall graph should behave.

For example, all inference graphs need to end with a single node, whether its a combiner combining multiple inputs, or a transformer, or a model--the graph can't split and then never rejoin, etc.

Is your feature request related to a problem?

No.

Provide a detailed description of the proposed feature

Please

Add Freebsd 12.1,12.2,12.3,13.0, 14.0 to the signatures.
Add OpenBSD
Add GhostBSD
Add NetBSD
Add Fedora 35

Alternatives you've considered

Additional information

(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.

Is your feature request related to a problem? Please describe.
It's cumbersome to create the same step twice.

Describe the solution you'd like
Add a button to duplicate a step in the pipeline editor.

Ideas
We could combine this with some other ideas in a context menu (right click).

Credit to Serhii Ostapchuk for contributing this on Slack.