workflows

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

https://user-images.githubusercontent.com/10436935/142174512-7b664879-0497-4517-b612-abb6ae1447b7.mov

Steps To Reproduce

Create an API data source and click on more actions menu

Environment

Release

Version

Self-Hosted

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

SUMMARY

I just faced an embarrassed problem that command st2 action list keeps return 503.

I tried st2 --debug action list and the result in line HTTP_PROXY(uppercase) was empty. This mislead me that the proxy info was set(which is not).

I finally found that the root cause is a lowercase http_proxy env variable was set in the system.

So I think it maybe more friend

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

App:
Nordigen

Link to developer documentation
https://ob.nordigen.com/api/docs

Actions:

• List transactions

Triggers:

• New transactions

Original request: PipedreamHQ/pipedream#1896

Is your feature request related to a problem? Please describe.
Each event received/emitted from event sources already has an event ID attached, so that it can be used in Sensor to achieve uniqueness, this ID is currently generated automatically. For some of the event sources like Kafka, we can extend the feature to generate a unique ID based on the original message, so that even there's a dup

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.