Create new job id for each file executed. #11
Closed
Conversation
This file contains hidden or 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
|
Just curious, why is |
Author
|
1000 > 1 :) Honestly, I don't remember. Probably an attempt to avoid id clashes, which do not even happen. |
fornwall
added a commit
that referenced
this pull request
Aug 5, 2019
Member
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Updating from old 0.3 I've noticed that only single (e.g. from 01, 02, 03 only 03) script from ~/.termux/boot gets executed on boot. Looks like this is because scheduling jobs with same id just replaces the previous one, so only one job ends up starting and sending task to the termux service.