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
Currently, the effective context_id is tracked by the host, but this results in a weird asymmetry between hostcalls (without context_id) and callbacks (with context_id), and makes it harder to build higher-level interfaces on top of those hostcalls.
In order to help with migration from v0.2 to vNEXT, we should accept context_id=0 as "context_id tracked by the host". This should be advertised via settings/feature flag and eventually removed.
The text was updated successfully, but these errors were encountered:
Currently, the effective
context_id
is tracked by the host, but this results in a weird asymmetry between hostcalls (withoutcontext_id
) and callbacks (withcontext_id
), and makes it harder to build higher-level interfaces on top of those hostcalls.In order to help with migration from v0.2 to vNEXT, we should accept
context_id=0
as "context_id
tracked by the host". This should be advertised via settings/feature flag and eventually removed.The text was updated successfully, but these errors were encountered: