Summary

Users often struggle to diagnoes templating problems. Helping them is time consuming. Everybody looses.

Instead, we log more diagnostics whenever resolution fails:

https://github.com/argoproj/argo-workflows/blob/9c901456a44501f11afc2bb1e856f0d0828fd13f/util/template/simple_template.go#L26

Several times here:

https://github.com/argoproj/argo-workflows/blob/9c901456a44501f11

Opened from the Prefect Public Slack Community

pat: This is a pretty minor problem as these things go, but it would be great if there was a way to disable the ASCII logo in Prefect Agent and Prefect Server, since it pollutes our server logs in DataDog. I can go hack the code, in Prefect, but it seems inelegant to have to re-apply such code after every version up

This issue is for developer to first contribute to dtm. It is for practice only, please just make changes to one file rather than all of them.

dtmsvr/trans_* files, add open source copyright comments, and send a PR for each file as a task

PR tutorial: https://opensource.com/article/19/7/create-pull-request-github
PR 中文教程: https://juejin.cn/post/6844903821521469448

If you are using Conductor at the company you work with, add the name of your company and your Github handle to the list at https://github.com/netflix/conductor/blob/main/WHOSUSING.md

Need to fix this TODO in the code:

         // TODO: we need to consider adding execution time to mutable state
	// For now execution time will be calculated based on start time and cron schedule/retry policy
	// each time DescribeWorkflowExecution is called.

https://github.com/temporalio/temporal/blob/master/service/history/historyEngine.go#L1184

Is your feature request related to a problem? Please describe.

It's not especially common to generate a certificate file which includes its own CA chain as well. The common case would be to have a shared CA chain file for each node, and then each node gets its own certificate (which other nodes cannot access). The Java client, for example, already works like this. Right now, for inter-clust

As reported by @jonalv , it can be confusing what is happening when if the globber pattern does not catch any files.

The suggestion is to:

• Log when the globber starts, with the pattern used
• Issue a warning if the globber doesn't match any files at all

Summary

What change needs making?
Example script on how to use created secret successfully.
I have tried myself using the following code from test
It creates a secret successfully but fails to echo the secrets value.

Use Cases

When would you use this?
when I n

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