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

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

Steps to reproduce:

1. Navigate to Home page
2. Click on organisation dropdown
3. Click on Rename of organisation
4. Add a long name to the organisation
5. Navigate to organisational Setting
   and observe the organisation name

Observation:
It is observed that the organisation name is not truncated

Expectation:
It is expected that when the organisational name is long it needs to be

The existing HTTP Request Trigger activity needs to be enhanced so that it allows users to have it generate a SAS token. The workflow will then only be triggered if the provided SAS token is valid. This prevents the workflow from being invoked by anyone other than those who have the full URL (including the SAS token appended as a querystring).

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

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

Is your feature request related to a problem? Please describe

A user on the mailing list wanted to clean the remote directories of all calculation jobs executed within a work chain with verdi calcjob cleanworkdir. Currently, this is not possible and I don't think there is a very straightforward way of doing this with the Python API.

Describe the solution you'd like

One solution

common-workflow-language/common-workflow-language#915

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.