Quinn Klassen

Thanks again for the bug report and reproduction. I filed an issue to track this here: https://github.com/temporalio/sdk-go/issues/1624

Thanks will include this in the next release for the resource tuner

Pausing and unpausing the deadlock detector is a **very** dangerous API, I do not think we should expose this to users as the potential for misuse far outweigh the legitimate...

We do not want to make it easier for users to disable deadlock detection. Disabling the deadlock detector in arbitrary sections of code should be difficult by design. >Described in...

No concern about the test format. Question about the general PR though, from the issue it says >The motivation for this is that, given appropriate tools, it will make it...

Hi https://github.com/temporalio/sdk-go/issues/1706 is now resolved and a fix will be included in the next release. The SDK will not correctly wait for the workflow tasks to finish before shutting down...

>However, they currently end up in an invalid state and [continue heartbeating](https://github.com/temporalio/sdk-go/actions/runs/14067722219/job/39394562700?pr=1885#step:6:811). The worker is not in any invalid state, it is waiting for the local activity to finish or...

>I added another commit setting ScheduleToCloseTimeout to 2 seconds and StartToCloseTimeout to 1 second, but the workflow task continues heartbeating for the entire duration of the test (15 seconds). Ah...

Marking as closed as since this does not appear to present compelling value to the Go SDK otel integration

Thanks, this is an improvement! The wording changes look good, there are some format things like adding quotes around variable that are not standard we should make sure we always...