Summary

Consider the following workflow:

apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: changing-conditional-
spec:
  entrypoint: plan
  templates:
  - name: plan
    steps:
    - - name: set-global-parameter
        template: global-parameter-setting
        arguments:
          parameters:
          - name: setting
            value: true

Current behavior

All ShellTask logs are logged at DEBUG level, preventing showing the command output in the UI logs unless the agent's logging threshold is set to DEBUG. But this is undesired for production workloads, as this applies to all log messages

streaming logging for the ShellTask was introduced in #3584

Proposed behavior

change existing stream_logs parameter to `U

Use Case

Right now users have no way to launch a pipeline run directly via the Python API (other than using the undocumented execute_launch_command function in the CLI module). We should add a blessed, documented way to launch a run via a Python function call. akin to execute_pipeline. This should be pretty straightforward, the only thing that's not 100% clear is what object we should use to i

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.

Hey everyone, I hope y'all enjoyed your holidays.
I want to create SuiteCRM users via the V8 api, but the response is invalid json and contains some generic validation error message.

I'm not sure whether my request is actually malformed or the error message just shouldn't appear.

Had the branch ancestry:

branch-1
  branch-2-bug-fix
    branch-3

All three branches had an open PR. branch-2-bug-fix‘s PR was a duplicate of a fix that someone else had already put in and merged at the same time. I closed the PR on branch-2-bug-fix and ran git town kill on that branch.

I was expecting it to change the base branch of branch-3‘s PR but instead it closed it