add a waiting reason when parallel updates has hit the max
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by tracing Tilt's max-update cap and the UI resource waiting-reason API described in the linked documentation. Determine where the global update limit is represented and how waiting reasons are exposed; done means capped resources show a stable reason without flapping as updates are scheduled.
Written by the indexing model from the issue text.
Description
Current Behavior
Tilt currently has a way to set the maximum number of parallel updates:
https://docs.tilt.dev/api.html#api.update_settings
Tilt also has an API for determining why a resource is waiting:
https://api.tilt.dev/interface/ui-resource-v1alpha1.html
But when a resource is pending because Tilt hit the maximum number of updates, there's no indication in the UI that this is the case!
Describe the Feature You Want
The waiting reason should say why the build hasn't started.
Additional context
The max update cap is handled separately from other kinds of "waiting" holds in tilt (because it depends on global state, rather than the state of a resource and its dependencies).
It's very important that "waiting" reasons don't "flap" back and forth between two reasons. For example, if you have 100 resources with the waiting reason "Number of updates maxed out", we don't want 99 resources to flip to a different reason, then flap to "Number of updates maxed out" when the new build is scheduled. This creates a lot of spurious updates that slow down the whole system.
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from tilt-dev/tilt
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 45/100
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
Tilt at scale Openenhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
blinklabs-io/bursa#904 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
yanet-platform/ipfw-go#129 ·
-
bug confmap/provider/googlesecretmanagerprovider needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
open-telemetry/opentelemetry-collector-contrib#51273 · 2 comments ·
-
bug: AI Gateway client filter lists "Unknown" twice when NULL and literal Unknown clients coexist Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100