Is your feature request related to a problem? Please describe.
Using Reset command with CLI will get code:deadline-exceeded message:timeout easily because reset requires replay in the server. It's quite resource consuming, depending on the length/size of the history.

By default the CLI context timeout is only 5 seconds:
https://github.com/uber/cadence/blob/63bdb5d7a04285cf57992c574639c9

Summary

The .alias property allows creating solids with names that would not pass the solid(name=...) validation. There seem to be two code paths for running this validation. These paths should be merged.

Reproduction

from dagster 

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

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

This could be example that uses these supported syntax and APIs:

https://github.com/couler-proj/couler/tree/d34a690/couler/core/syntax

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.

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

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

Expected Behavior

A human readable string that indicates that workflow is closed.

Actual Behavior

3 INVALID_ARGUMENT: java.lang.Error: closed at
io.temporal.internal.sync.DeterministicRunnerImpl.checkClosed(DeterministicRunnerImpl.java:433) at 
io.temporal.internal.sync.DeterministicRunnerImpl.stackTrace(DeterministicRunnerImpl.java:418) at 
io.temporal.internal.sync.SyncWorkflo