Improve Spectrum-X CIDRPool allocation errors - #147
Merged
Conversation
Signed-off-by: Alexander Maslennikov <amaslennikov@nvidia.com>
Greptile SummaryImproves Spectrum-X CIDRPool and template-rendering error diagnostics without changing allocation semantics.
Confidence Score: 5/5The PR appears safe to merge, with no concrete changed-code defect identified. The new logic is confined to bounded diagnostic formatting and a shared pool-key helper, while exact node filtering, pool construction, and template rendering behavior remain intact. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[Load Spectrum-X topology] --> B[Build normalized host links]
B --> C[Filter links by exact worker-node names]
C --> D{Any matching pool keys?}
D -- No --> E[Report selected workers, topology hosts, missing workers, and mismatch hint]
D -- Yes --> F{Every selected worker present in each pool?}
F -- No --> G[Report missing workers and available rail or plane coverage]
F -- Yes --> H[Render CIDRPools with unchanged allocation semantics]
Reviews (1): Last reviewed commit: "Improve Spectrum-X CIDRPool diagnostics" | Re-trigger Greptile |
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.
Summary
Allocation semantics are unchanged: l8k still requires exact, case-sensitive node-name matches and does not auto-match similar names.
Testing
go test ./...go build ./...go run github.com/golangci/golangci-lint/v2/cmd/golangci-lint@v2.11.0 run ./...mkdocs build --strict