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 Nov 10, 2020. It is now read-only.
I would think each message processed leads to adding a number of messages to the queue and then returns synchronously, but for some reason, if you don't use a setTimeout between propagate iterations in test/helpers/graph.js, it reaches maximum callstack size. A console.log statement in each iteration also does the job, which means that console.log is not a usable method to investigate this problem. :)
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I would think each message processed leads to adding a number of messages to the queue and then returns synchronously, but for some reason, if you don't use a setTimeout between propagate iterations in test/helpers/graph.js, it reaches maximum callstack size. A console.log statement in each iteration also does the job, which means that console.log is not a usable method to investigate this problem. :)
The text was updated successfully, but these errors were encountered: