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

I made a "dagster-internal" resource (instead of "dagster_internal") and didn't find out that was a problem until pipeline execution: https://dagster.phacility.com/P231

We should have everything we need to disallow that at definition time

lowdefy/lowdefy#540 (comment)

Currently such a request would return an HTTP 500:

curl -H "Authorization: Bearer <valid token>" "http://localhost:7575/v1/packages/not-a-real-package-id"

I believe this is unexpected and an HTTP 404 would be more appropriate, which would mean (specification):

10.4.5 404 Not Found

The server has not found anythi

Summary

The current implementation does not allow creating templates specifying the parallelism field as per the Argo spec.

Use Cases

Many possible use cases, my current one is limiting the amount of parallel nodes running a certain template so as to save

We should have a group support to handle permissions access from a LDAP, SSO, ...

allowed_resolvers_groups on templates for example.
admin_groups on configuration for example.

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.

As of alpha 2.685 there's a new action trigger_named_async_without_response which can be used in favor of trigger_named. Wrapper does not operate on trigger response anyway, so using the new method which works better for broader spectrum sounds like a good idea. More on that here: https://community.folivora.ai/t/floating-html-settings-menu/5788/44?u=worie

1. Setup the project locally or visit the demo site here https://imvetri.github.io/ui-editor/
2. Click Components->Div. Div is a recursive component that can move, resize, draw more divs within it and add text. These options are available because of the select option.
3. Remove select from Div and create it as a new component "Select".
4. Use Select component within the Div component.
5. If it

The AA user group is currently referenced in the README. It's very quiet. This doesn't look good for project activity. Should we a) retire it, b) commit to using it more?

Personally, I find github issues much more useful for keeping on top of things.

https://groups.google.com/forum/#!forum/automaticanalysis