workflow
Here are 2,501 public repositories matching this topic...
-
Updated
Nov 10, 2020 - TypeScript
-
Updated
Nov 10, 2020 - TypeScript
-
Updated
Nov 4, 2020 - JavaScript
Summary
I expect CLI docs to tell end user differences between argo terminate and argo stop intentions and its expected behavior. I found none.
Diagnostics
What Kubernetes provider are you using?
AWS
What version of Argo Workflows are you running?
2.16
**Message from the
-
Updated
Jul 31, 2020 - JavaScript
Context
Currently, when prefect.tasks.shell.ShellTask is invoked with return_all=True, the shell task will not log the stdout through logger.debug.
This is defined in doc
https://docs.prefect.io/api/latest/tasks/shell.html#shelltask
and implement in the code.
https://github.com/PrefectHQ/prefect/blob/73fe1eb57945fc13bdd36b361a6a17c3f324b1ba/src/prefect/tasks/shell.py#L107-L111
-
Updated
Nov 6, 2020 - Go
-
Updated
Nov 9, 2020 - JavaScript
-
Updated
Oct 17, 2020
-
Updated
Nov 3, 2020 - Shell
-
Updated
Nov 3, 2020 - C#
-
Updated
Jul 2, 2020 - C#
-
Updated
Sep 28, 2020 - PHP
Currently, the repository name and repository location name are just displayed next to each other in the Dagit repository picker.
We should make it more obvious about which one is which. This would help expose the concept of repository locations to the user as well.
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
-
Updated
Oct 20, 2020 - Python
-
Updated
Nov 8, 2020 - Java
-
Updated
Jul 30, 2020 - CSS
-
Updated
Oct 6, 2020 - JavaScript
-
Updated
Oct 27, 2020 - Python
-
Updated
Oct 11, 2020 - JavaScript
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
-
Updated
Nov 6, 2020 - Python
-
Updated
Sep 4, 2020 - JavaScript
-
Updated
Nov 10, 2020 - Java
Improve this page
Add a description, image, and links to the workflow topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the workflow topic, visit your repo's landing page and select "manage topics."
Description
Variables on Airflow are required to be defined in JSON format but it's very hard to edit JSON on the current UI. Then it's much better if the editor variables UI on Airflow are updated to support JSON format instead of plain text.
Use case / motivation
The editor for variables is much better if it can highlight keywords and validate the content.
Related Issues