You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
.NET currently applies jobs without reordering them (or, as I'm writing this, potentially will as a temporary workaround until we address this), but wakes up the event loop after each job.
There is a really nice test here@mjameswh added that I think all async languages should have some form of that helps us understand exactly how routines will proceed.
I'm not sure if making this change will actually have consequences to the realized .NET behavior. In any case it should probably be protected with a flag if we make it.
We decided not to merge this since it requires a flag, and this change alone doesn't quite justify one. However, if #386 is done it would make sense to gate this behind the same flag.
.NET currently applies jobs without reordering them (or, as I'm writing this, potentially will as a temporary workaround until we address this), but wakes up the event loop after each job.
In TS, we changed this to apply jobs to state and then run the event loop: temporalio/sdk-typescript#1488
There is a really nice test here @mjameswh added that I think all async languages should have some form of that helps us understand exactly how routines will proceed.
I'm not sure if making this change will actually have consequences to the realized .NET behavior. In any case it should probably be protected with a flag if we make it.
See temporalio/sdk-python#606 for python equivalent
The text was updated successfully, but these errors were encountered: