Run monitorFn always on start #26 #28
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
m-mohr
force-pushed
the
run-monitoring-at-start
branch
from
bf4b350
to
f39bac5
Compare
m-mohr
force-pushed
the
run-monitoring-at-start
branch
3 times, most recently
from
fa2f14f
to
ab09cbc
Compare
m-mohr
force-pushed
the
run-monitoring-at-start
branch
4 times, most recently
from
fa31c47
to
2512a4e
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.
Fix bug: use setInterval instead of setTimeout
Call callback once always at the start to pass the job info also if there are no new jobs.
Issue: #26