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

I'd like to be able to debug cadence's space usage by breaking down the size of history events by workflow type. But currently I cannot.

Proposed Solution

Proposed by @longquanzheng in the cadence slack: track a historySize in ES so we can query it for aggregation.

Additional context

https://uber-cadence.sl

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

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

Describe the bug

The section on creating a service account in the Google Cloud console is out of date

Receive events from MSK with IAM auth config https://docs.aws.amazon.com/msk/latest/developerguide/iam-access-control.html

It would be nice if doit could use as many processes as there are CPUs instead of only a hardcoded number.

Remove this porting helper added in #13938.

Issues to fix known callers:

• #13923
• #13921
• #13973

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.

Currently each Observer support state management.

Obsei store state in any of sqlalchemy supported database on schema mentioned in WorkflowTable class.

There is example also exist to show it's capability.

State m

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

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

Expected Behavior

Temporalite could create the directory first, then start writing to the database file.

Actual Behavior

User sees an error message like

2022/04/04 18:57:43 error setting up schema: unable to create SQLite admin DB: unable to open database file: no such file or directory

The error text doesn't include the file path that is being opened, which makes un

What should we add?

0.0.0.0 is a special reserved IP and shouldn't be used to run the server. https://en.wikipedia.org/wiki/0.0.0.0

We should use localhost in docs instead.

Maybe the covalent start output can be enhanced so that it's more like Jupyter.

    To access the server, open this file in a browser:
        file:///Users/scott/Library/Jupyter/runtime/jpserver-15858-ope