Summary

Backend error: Exit status: 500, message: {"Type":"ExecutableNotFoundError","Message":"OCI runtime exec failed: exec failed: container_linux.go:349: starting container process caused \"exec: \\\"bash\\\": executable file not found in $PATH\": unknown","Handle":"","ProcessID":"","Binary":""}

Steps to reproduce

Use @vito buildkit container, or any container which doe

Use case

Polyaxon tracking can be used to automatically log all information generated by Ludwig.

We should probably think about adding support for Polyaxon's tracking module in Ludwig contrib.

Problem
Since Java 8 was introduced there is no need to use Joda as it has been replaced the native Date-Time API.

Solution
Ideally greping and replacing the text should work (mostly)

Additional context
Need to check if de/serializing will still work.

Is your feature request related to a problem? Please describe.
SNS endpoint subscriptions must expose a public facing HTTP server ( unless I missed something ) and therefore make it possible for untrusted sources to post messages to the event bus as long as the message comply with basic message format.

Describe the solution you'd like
The SNS source should verify the signature of the

Currently one can only start a pipeline run (local and on kubeflow pipelines) from the Pipeline Editor. By adding the ability to somehow start a run from the command line Elyra users could take advantage of features that are not available in Elyra or JupyterLab, such as automation or scheduling

For example:

• User X creates a pipeline and tests it using the UI
• Once satisfied that it produc

Hi!

When using the unprivileged image, it's not possible to load custom configurations.

# podman run -p 8080:8080 -e GITLAB_MONITOR_CONFIG=/tmp/config.json timoschwarzer/gitlab-monitor:unprivileged
/wrapper.sh: line 4: can't create /usr/share/nginx/html/config.json: Permission denied

Indeed, root is needed to create a new file in /usr/share/nginx/html, and it looks like wrapper.s

In the docs -- https://github.com/tektoncd/triggers/blob/master/docs/eventlisteners.md#serviceaccountname -- it states that ServiceAccountName is required. In our environment an EventListener author would never know what ServiceAccounts are available so we would like to use "default" in this case or better still follow Tekton Pipelines logic -- https://github.com/tektoncd/pipeline/blob/db66eca6112