Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Steps To Reproduce

Go the Get documents in collection command in Firestore queries

Environment

Production

V

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.

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

Actions

• Create an Item | Creates an item
• Update Item Name | Update an item's name
• Create a Board | Creates a new board
• Create a Group | Creates a new group in a specific board
• Create an Update | Creates a new update

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/

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