Repository navigation
feat(computing-unit-managing-service): say how to free a slot when the CU quota is reached - #8772
Merged
Xiao-zhen-Liu merged 4 commits intoNov 7, 2026
Conversation
…e CU quota is reached The quota error only said "You may only have N computing-unit(s) running at the same time". It now adds: "Reuse one of your running computing units, or terminate one you no longer need." Refs TEX-86 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> (cherry picked from commit 58999cc)
Contributor
Automated Reviewer SuggestionsBased on the
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #8772 +/- ##
============================================
- Coverage 92.17% 92.17% -0.01%
- Complexity 4987 4988 +1
============================================
Files 1284 1284
Lines 55605 55599 -6
Branches 7120 7120
============================================
- Hits 51255 51249 -6
Misses 2591 2591
Partials 1759 1759
*This pull request uses carry forward flags. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Contributor
Author
|
/request-review @Xiao-zhen-Liu |
Xiao-zhen-Liu
approved these changes
Oct 6, 2026
…or each unit type Local units count toward the running-unit limit too, and the UI removes them with "Disconnect" (the same terminate call, which frees the slot). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Author
|
Fixed: the hint now says which action frees a slot for cloud and local units. |
…ently and name Kubernetes units "computing-unit(s)" becomes "computing unit(s)" to match the rest of the message, and "cloud unit" becomes "Kubernetes unit", which is what the UI calls them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
github-merge-queue
Bot
removed this pull request from the merge queue due to no response for status checks
Oct 15, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to no response for status checks
Oct 21, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to no response for status checks
Oct 22, 2026
Contributor
Author
|
@Xiao-zhen-Liu can you add this and #8770 and #8771 to merge queue again? |
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
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.
What changes were proposed in this PR?
When a user hits the computing unit limit, the error only said "You may only have N computing-unit(s) running at the same time". It now adds what to do: "Reuse a running computing unit, terminate a cloud unit, or disconnect a local unit you no longer need." Local units count toward the limit too, and the UI removes them with "Disconnect", which calls the same terminate endpoint and frees the slot.
Any related issues, documentation, discussions?
Part of #8736. Split out of #8737.
How was this PR tested?
Updated
ComputingUnitManagingServiceExceptionSpec.There's no screenshot because this error only appears on a Kubernetes deployment, and I tested on a local install.
Was this PR authored or co-authored using generative AI tooling?
Generated-by: Claude Code (Claude Opus 5.5)