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
Since host functions can't actually be interrupted, it might make sense to not include them in the overall timeout. If we do that we could then give the user some more fine grained controls for managing timeout from within host functions.
The text was updated successfully, but these errors were encountered:
at least from a .Net perspective it would be great to support cancelation tokens ? A how function may call our to other services, that in turn support cancelation, so the cancelation token can be passed along.
I guess that other languages may have similar constructs. The is also related to the need/desire that host functions could could be asynchronous (albeit seem work here was abandoned per the PR: #264) - are there any timelines/plans get back to this?
Since host functions can't actually be interrupted, it might make sense to not include them in the overall timeout. If we do that we could then give the user some more fine grained controls for managing timeout from within host functions.
The text was updated successfully, but these errors were encountered: