queue handling evaluations #4
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
deanrad
force-pushed
the
queue-handling-evaluations
branch
from
8f7cf0e
to
94aed26
Compare
deanrad
force-pushed
the
queue-handling-evaluations
branch
from
94aed26
to
f590632
Compare
deanrad
force-pushed
the
queue-handling-evaluations
branch
from
bc4ac15
to
60ed61c
Compare
deanrad
force-pushed
the
queue-handling-evaluations
branch
3 times, most recently
from
3de78b8
to
dd0fb0b
Compare
deanrad
force-pushed
the
queue-handling-evaluations
branch
from
dd0fb0b
to
e0a6da5
Compare
deanrad
force-pushed
the
queue-handling-evaluations
branch
from
e0a6da5
to
d8a1af8
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Doesn't insert an artificial amount of time between triggerings, but ensures the filters/listeners for an event run completely before beginning to run them for the next event. This ensures listeners always agree on event order, and should prevent a stack overflow error should triggerings ever recursively call.
Fixes #2