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
{{ message }}
This repository has been archived by the owner on Dec 13, 2019. It is now read-only.
Currently, if two Nodes that have a channel with each other simultaneously dispatch calls in which this channel is operated on, the state of the channel can get modified that effect the execution of the protocols (i.e. signature verification on differing channel states).
This happens because:
there are no global queues for the clients to look up which channels are "locked" (i.e. being operated on) (since only local queues exist)
the checks for whether a protocol is already in execution on this channel such that the incoming operation should be awaited is seemingly faulty
The text was updated successfully, but these errors were encountered:
cf19drofxots
changed the title
[node] Sync issue on multiple protocols being executed across clients
[node] Insufficient awaits for multiple protocols being executed across clients
Sep 6, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently, if two Nodes that have a channel with each other simultaneously dispatch calls in which this channel is operated on, the state of the channel can get modified that effect the execution of the protocols (i.e. signature verification on differing channel states).
This happens because:
The text was updated successfully, but these errors were encountered: