SUMMARY

Errors are generated in /var/log/st2/st2rulesengine.log even though the rule is run successfully with out issues.

STACKSTORM VERSION

# st2 --version
st2 3.2.0, on Python 2.7.5

OS, environment, install method

# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.8 (Maipo)

Installed with Puppet module

Steps to reprod

In case of visibility record not consistent with workflow execution, it's good to have a CLI cmd to update doc, similar to delete doc.

As I was following the tutorials, I discovered that they Keywords screen has changed. Now there are two options for input: "with input as argv", "with input as {query}". The option "with input as argv" is selected by default.

Tutorial is written using "with input as {query}", so initially it doesn't match on the screen. There is no option to choose the Escaping options in the "with input as arg

It would be helpful to understand which versions of Django have been tested and/or are supported. For example, does Wooey work with Django 2.0 or higher? If not, it would be helpful for myself and others who might want to use Wooey on Django 2+ to be able to contribute pull requests.

Example:
Run this tool (provide any directory as the aa input)

class: CommandLineTool
cwlVersion: v1.0
baseCommand: ["echo"]
inputs:
- type: Directory
  id: aa
  inputBinding:
    valueFrom: "$(self.listing.length)"
outputs:
  o1:
    type: Directory
    outputBinding:
      glob: $(inputs.aa.basename)
requirements:
- class: InlineJavascriptRequirement
- class: InitialWork

Is there a way to trigger a workflow from another workflow? Example:

1. Trigger inner workflow, halt workflow until inner workflow is done.
2. Inner workflow is complete, based on completed workflow state, proceed with workflow.

If this feature cannot be done with the current code, any pointers on how to implement one?

My first thought would be a combination of ReceiveHttpRequest/WriteH

Describe the bug
Github Gateway pod unable to create webhook because of trailing whitespace that gets appended to the webhook token in the header
Is this a bug? YES
Is there a deployment method to prevent it?

Environment (please complete the following information):

OS: macOS Mojave 10.14.4
minikube: v1.0.1
Helm: v2.14.0
argo workflow: v2.2.1
Argo-events: v0.9.2

In web installer, Instructions guides link are really needed at each step for better support.

some of the links should be shown at the header

1. Need Help?
2. forum
3. Installation Guide
4. Developer Guide

Inspired by common-workflow-language/common-workflow-language#125 (comment)

And if not, do we want it to?

The current codebase requires ElasticSearch 6 (we currently test with 6.8.8). Please document this requirement (and maybe provide for clear error handling in the code when this requirement is not met,
to provide for better user experience).

( related: #313 )

I am not sure if this belongs here, but I am having an issue when using this Github Action.

This is the link to the github run that failed:
https://github.com/jampp/migratron/pull/25/checks?check_run_id=456554120

and the content is:

Uploading distributions to https://test.pypi.org/legacy/
Uploading migratron-1.1.0-py3-none-any.whl

  0%|          | 0.00/30.5k [00:00<?, ?B/s]
100%|

The assert_executable_exists(cmd) function checks for the presence of an executable in the environment where the workflow is executed.

So, we can utilize this function to check for the presence of the required binaries/executables through the __init__() method(constructor) of the concerned runner classes, like [`run

the basic tfadd is stupid, need to learn tensorflow distributed well enough to do (perhaps) a distributed add based on number of nodes. Also it should exit when the job is finished, not just timeout.

We can add generation of derived documentation via tsdoc/typedoc or similar then apply fork of docdash: https://github.com/clenemt/docdash

"script": {
"generate-docs": "node_modules/.bin/jsdoc -c jsdoc.json"
}
This way we can have standalone documentation showing how to use the library.

Allowing easy ssh into it and debugging.

This should be supported at the Ketrew level, an optional capability of each backend, I think.

Add additional cloud-watch logging integration for steps involved with instance configuration. This will improve developer ability to isolate and debug user issues