Hello,

Core operators have not moved to new AIP-21 compliant modules.
In most cases this means that the _sensor or _operator suffixes need to be deleted from the module name and in place of the old module a class deprecation warning should be added.

After making a change to the master branch, the

Summary

What happened/what you expected to happen?

I navigated to the main workflows page http://localhost:2746/workflows/argo and received an error with a stacktrace. I expected to see my workflows listed.

Diagnostics

What version of Argo Workflows are you running?
2.11.0

At some point the main argo workflows page started throwing an error in my Chrome browser. I haven't be

Created by Dylan Hughes via monday.com integration. 🎉

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.

Issue

16 files has some sort of Sugar Pro references in code as comments.
Those should be removed

Steps to Reproduce

Try the search with BEGIN: pro
https://github.com/salesagility/SuiteCRM/search?q

name the threads we spawn so debug output is more useful

https://docs.python.org/3/library/threading.html#threading.Thread

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