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

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

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

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

Follow up for #197 and #215

• Fix the ORDER BY issue so that we don't accidentally overwrite extra dispatch IDs https://github.com/AgnostiqHQ/covalent/pull/215/files#diff-d5a1b52ef809a88edbb01367cf4a161ddc0b9ce35c885981d8a8363cb0588949R151
• Figure out why middleware doesn't work https://github.com/AgnostiqHQ/covalent/pull/215/files#diff-d5a1b52ef809a88edbb01367cf4a161ddc0b9ce35c8859