Chad Retz

Ah, that may be different (this issue is for queries during retry in particular). Can you open a new issue? Also, you are looping through issues more than twice, e.g....

Update for those reading this issue. The primary issue here (last few comments a different thing) is https://github.com/temporalio/temporal/issues/2300.

This may be solved with https://github.com/temporalio/temporal/pull/2826. Once released, we will write a test confirming that queries can be issued during workflow retry or cron or pending continue as new.

An issue like this has also been fixed in #741. Despite my best efforts, I have not been able to replicate this concurrent map write and it may have been...

@thomashusa - Is it possible to replicate this in anyway somewhat reliably? Using the `-race` flag could make it more likely to happen. This can intentionally happen if you're using...

> Can you give some example consumers for this API? Users who want to only skip tracing headers > I guess I'm wondering why not just pass a list of...

We have not prioritized this because there haven't been many requests. Are you needing dynamic activity/workflow support? In almost all cases, a properly named/registered activity/workflow should be used and field...

Something like: ```go func FallthroughWorkflow(ctx workflow.Context) error { workflow.GetLogger(ctx).Info("Called workflow: " + workflow.GetInfo(ctx).WorkflowType.Name) } func FallthroughActivity(ctx context.Context) error { activity.GetLogger(ctx).Info("Called activity: " + activity.GetInfo(ctx).ActivityType.Name) } func Register(worker worker.Worker) error {...

Waiting on SDK consensus here.

Can you use `errors.As` instead, e.g.: ``` var panicErr *temporal.PanicError if errors.As(err, &panicErr) { fmt.Printf("Got panic error, trace: %v", panicErr.StackTrace()) } ```