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
On the development environment, are being called simultaneously and resulting in unexpected behaviors.
Actually, blocks are being mined so shortly that a listener for a block is being called before of the call from the last block.
For now, a call will be ignored if has another call running.
Comment extracted from: tasit-action > Action.js > #addConfirmationListener:
// Note:// On the development env (using ganache-cli)// Blocks are being mined simultaneously and generating a sort of unexpected behaviors like:// - once listeners called many times// - sequential blocks giving same confirmation to a transaction// - false-positive reorg event emission// - collaborating for tests non-determinism//// Tech debt:// See if there is another way to avoid these problems, if not// this solution should be improved with a state structure identifying state per event//// Question:// Is it possible that that behavior (listener concurrent calls for the same event) is desirable?
Is the non-determinism mostly for tests where the listener is added before or after sending the tx? Or is it a little of both?
We're sure it's not just getting called again with another confirmation for each instantaneous block, right? If so, we could probably disable that in our code and check number of confirmations on each listener call. Or something like that.
On the development environment, are being called simultaneously and resulting in unexpected behaviors.
Actually, blocks are being mined so shortly that a listener for a block is being called before of the call from the last block.
For now, a call will be ignored if has another call running.
Comment extracted from:
tasit-action
>Action.js
>#addConfirmationListener
:Extracted from: #369 (comment)
The text was updated successfully, but these errors were encountered: