Chad Retz

This is going to be tough to do. Notes: * We have to be able to use the primary/user-controlled event loop for running (some) activities/operations anyways, so maybe this is...

I'd be ok for now raising an exception for if the `activity.client()` is invoked in `def` activites (so `async def` activities only for now)

:+1: Should just not call `set_result` on an already done future (and find where else we might be doing that). This is probably just us (me) not properly thinking about...

Features issue made at https://github.com/temporalio/features/issues/624. Please refer to that for ideal behavior.

I think that's divorcing it a bit too much ```yaml commands: temporal env set: summary: Set environment properties description: | `temporal env set --env environment -k property -v value` Property...

So I have some backtraces from gdb like: ``` #0 0x00007ffcc22b7618 in x64-ucrt-ruby330!rb_w32_Sleep () from c:\dls\ruby-3.3.5\bin\x64-ucrt-ruby330.dll #1 0x00007ffcb14fc9a2 in parking_lot::raw_mutex::RawMutex::lock_slow () from c:\work\tem\sdk-ruby\temporal-sdk-ruby\temporalio\lib\temporalio\internal\bridge\temporalio_bridge.so #2 0x00007ffcb14e3568 in tokio::runtime::blocking::pool::Inner::run () from c:\work\tem\sdk-ruby\temporal-sdk-ruby\temporalio\lib\temporalio\internal\bridge\temporalio_bridge.so...

It is on our relatively-near-term backlog, but no updates at this time

> Here is a simple code to reproduce bug: I am struggling to replicate. There is a slight bug where `run` accepts `self`, but fixing that, I didn't see it....

Thanks! We will increase the priority on this.

> that client destructor might be called even during execution process (not only at exit), when there is no references to the object. This is not just about client destructor,...