workflows

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Update labelSend client credentials with to Send client credentials with (on refresh token): under the Advanced settings tab that appears for Oauth + Authorization Code setting.

Steps To Reproduce

1. Create new Rest API datsaource.
2. Set authentication typo to OAuth.

Is your feature request related to a problem? Please describe.
Need to search using LIKE operator with search attributes? eg, WorkflowType LIKE workflowType-prefix.*
Right now the workflowType is using keyword type for performance reason so it doesn't support wildcard search.

https://www.elastic.co/guide/en/elasticsearch/reference/current/keyword.html

keyword fields are untokeniz

Apart from Unit and Integration tests, we should also run the st2-self-check script for every PR as part of the CI pipeline.
Something we do in e2e and manual testing.

It should be possible with the Github Actions and would help us to catch bugs before merging into master.
Ex #5489.

Need to fix this TODO in the code:

         // TODO: we need to consider adding execution time to mutable state
	// For now execution time will be calculated based on start time and cron schedule/retry policy
	// each time DescribeWorkflowExecution is called.

https://github.com/temporalio/temporal/blob/master/service/history/historyEngine.go#L1184

Currently Swashbuckle only looks at controller actions when building an Open API specification. We should look into the possibility of telling Swashbuckle to also look at HTTP Endpoint activities declared on workflow blueprints. This would provide a complete view of all of the exposed API endpoints when generating the specification.

CloudTables
https://cloudtables.com/docs/cloud/api/rest

Actions

• Insert row: Create a new row.
• Update row: Edit an existing row.
• Delete row: Delete a row.

Receive events from MSK with IAM auth config https://docs.aws.amazon.com/msk/latest/developerguide/iam-access-control.html

Sending a rest call to delete a job specification throws 404 where as grpc call works fine. Steps to reproduce

curl -X DELETE "http://localhost:9100/v1/project/my-project/namespace/kush/helloworld" -H  "accept: application/json"

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%|

Describe the bug
Deploying a new job, then pulling logs via the CLI results in a panic (SIGSEGV).

To Reproduce

1. odin deploy -f test.job.yaml
2. odin log -i {job_id}

vagrant@vagrant:~/odin$ odin log -i dea194794589
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x40 pc=0x79c764]

goroutine

New documentations not found.

Examples:

This page:
https://aiida.readthedocs.io/projects/aiida-core/en/v1.0.0/_modules/aiida/backends/tests/orm/utils/test_loaders.html
directs to a newer version, which is non-existing:
https://aiida.readthedocs.io/projects/aiida-core/en/v1.6.4/_modules/aiida/backends/tests/orm/utils/test_loaders.html

This page:
https://aiida.readthedocs.io/projects/

Expected Behavior

A warning when format is used with an invalid type.

Actual Behavior

Validation passes with no warnings/errors.

Workflow Code

https://cwl.discourse.group/t/potential-defect-in-ontology-format-checking/529

Full Traceback

NA

Your Environment

• cwltool version:
  3.1.20220204090313

Add an example workflow in the examples/gradle/ folder that exemplifies how to make use of Popper to create a CI pipeline for java projects that use gradle as their build system. The image used by the workflow can be the official one.