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
In Go, there was some confusion about if Futures run even if you don't Select() but the docs say:
selector.Select(ctx) is the primary mechanism which blocks on and executes Future work. It is intentionally flexible; you may call it conditionally or multiple times
This seems to conflict with other docs that say things like "ExecuteActivity requests activity execution in the context of a workflow...ExecuteActivity immediately returns a Future that can be used to block waiting for activity result or failure."
So does the Select() let you block while the activity runs or does it actually execute the activity?
I was sure it's nothing runs until you call selector.Select(ctx) from this comment:
// API Example: block until the next Future is ready to run
// important! none of the deferred code runs until you call selector.Select
This was confirmed by testing I did today.
But my pause is about the docs which say "request execution". It seems it might be more clear if it says "requests execution to be done upon get() or select()".
I think that could be a good clarification.
more discussion here
The text was updated successfully, but these errors were encountered:
Temporal Affiliation
Content Suggestion
In Go, there was some confusion about if Futures run even if you don't Select() but the docs say:
This seems to conflict with other docs that say things like "ExecuteActivity requests activity execution in the context of a workflow...ExecuteActivity immediately returns a Future that can be used to block waiting for activity result or failure."
So does the Select() let you block while the activity runs or does it actually execute the activity?
I was sure it's nothing runs until you call selector.Select(ctx) from this comment:
// API Example: block until the next Future is ready to run
// important! none of the deferred code runs until you call selector.Select
This was confirmed by testing I did today.
But my pause is about the docs which say "request execution". It seems it might be more clear if it says "requests execution to be done upon get() or select()".
I think that could be a good clarification.
more discussion here
The text was updated successfully, but these errors were encountered: