workflows

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Misalignment of Close and delete icon when the user has a long page

Steps To Reproduce

1. Go to page setting tab
2. Click on gear icon
3. inside the pop up verify the display of delete and close icon

Environment

Release

Version

Cloud

e.g. resetType of LastDecisionCompleted isn't able to reset the failed activity which failed a workflow. In this case, if using a offset of -1 will help.

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.

Is your feature request related to a problem? Please describe.
There is an optional config for namespace called "sampled retention days" that can be specified when create a namespace. It was created long ago as workaround for long retentions before long term archival was available.

Describe the solution you'd like
We should get rid of the sampled retention.

**Describe alternatives

The "WorkflowInstances.Retry" OperationId is duplicated in multiple api controllers.

See the swaggeroperations attributes of the following controllers:

BulkRetry.cs
Cancel.cs
Retry.cs

Update:
"operationId": "Signals.Execute", is also duplicate

Is there a specific app this action is for?

Please provide a link to the relevant API docs for the specific service / operation.

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"

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

The files on PyPI have these hash values:

• SHA256
• MD5
• BLAKE2-256

If print the hash values, people can easily verify whether the file on PyPI was automatically uploaded by CI script.
It is best to print a pretty-print table.

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/

And link to https://github.com/common-workflow-language/cwl-utils#pull-the-all-referenced-software-container-images

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.

Is your feature request related to a problem? Please describe.

To match the current pattern for building Workflows it would be great to be able to end the build chain with
eraseToAnyWorkflow. This would follow other modern swift paradigms (example AnyPublisher).

Describe the solution you'd like

Create an extension method on Workflow that will return the current Workflow erased as