Is your feature request related to a problem? Please describe.
It will make uber/cadence-web#281 possible

Proposed Solution
Return the data from this value: https://github.com/uber/cadence/blob/d0a8f7e6a9297bd898ea5b10ded20f0277a8980f/service/frontend/adminHandler.go#L190

add this to the existing API “describeCluster”

follow these two PRs:
https://gi

Use Case

just like we now do for solid

i.e. make these two equivalent:

@pipeline(description="""
    abc
    123
""")
def my_pipeline():
    ...

@pipeline
def my_pipeline():
    """
    abc
    123
    """
    ...

Ideas of Implementation

Additiona

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

What happened/what you expected to happen?

We expect the container use the existing volume defined inside the workflow. Such as:
volumes-existing.yaml

example for testing:

import os

import couler.argo as couler
from couler.argo_submitter import ArgoSubmitter
from couler.core.t

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

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

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

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