Repository navigation
fix(bash): stop finished jobs from using up the background job budget - #3869
Open
taciturnaxolotl wants to merge 1 commit into
Open
taciturnaxolotl wants to merge 1 commit into
taciturnaxolotl wants to merge 1 commit into
Conversation
taciturnaxolotl
force-pushed
the
fix/background-job-budget
branch
from
September 18, 2026 19:29
7f64baf to
85a7876
Compare
taciturnaxolotl
force-pushed
the
fix/background-job-budget
branch
3 times, most recently
from
September 21, 2026 21:35
445386a to
d4d367e
Compare
Member
|
@taciturnaxolotl can we get this in config for overrides? always good to include it For users who think 50 bg jobs is good and want to run them |
taciturnaxolotl
force-pushed
the
fix/background-job-budget
branch
8 times, most recently
from
September 29, 2026 02:49
d88b736 to
48e28ff
Compare
taciturnaxolotl
force-pushed
the
fix/background-job-budget
branch
3 times, most recently
from
October 10, 2026 04:57
7c655e5 to
921d4be
Compare
taciturnaxolotl
force-pushed
the
fix/background-job-budget
branch
4 times, most recently
from
October 14, 2026 13:18
12a98db to
62c1755
Compare
Background jobs counted toward the 50-job cap even after they finished, and a finished job lingered for eight hours. Once fifty had piled up, every bash command failed to start, including ones that take milliseconds. Parallel sub-agents share one budget, so they filled it quickly. Only running jobs hold a slot now. Finished jobs stay readable but are dropped oldest-first once the tracked total gets large. wip: configurable bg job budget wip: tnr follow-ups
taciturnaxolotl
force-pushed
the
fix/background-job-budget
branch
from
October 14, 2026 17:47
62c1755 to
0ac04e4
Compare
Member
Author
|
added to the config! |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Crush counted finished background jobs against the 50-job limit, so once enough jobs had finished, new ones were refused even though nothing was running.
Now only running jobs count against the limit. Finished jobs keep their output readable for 8 hours, and at most 250 of them are kept; the oldest are dropped first.
The running limit is configurable and takes effect when the config reloads:
or
options.max_background_jobsincrush.json. Zero or a negative value means the default of 50.