Skip to content

fix(locate): search resolved models in parallel - #235

Merged
orian merged 1 commit into
mainfrom
feat/locate-resolved-model-search
Sep 7, 2026
Merged

orian merged 1 commit into
mainfrom
feat/locate-resolved-model-search

Conversation

@orian

@orian orian commented Sep 7, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • change table/column lookup to load and resolve models before searching them
  • compose every manifest role/environment stack, treat the ordered -layer list as one model, and load every dump file as an independent node model
  • load independent models through a bounded 32-worker pool while preserving deterministic result order, allowing all 30 nodes in a typical cluster to load concurrently
  • search final resolved table columns so inheritance, patches, modifications, overrides, and drops are reflected
  • return each matching manifest, layer, or dump model in text and JSON output and update the public documentation

End-to-end coverage

  • run the CLI in a subprocess for the multi-table/multi-column report, empty-success behavior, and malformed-input failure
  • run the CLI in a subprocess against 30 real node dump files and verify all 30 resolved model references
  • use a worker barrier test to prove 30 loads start concurrently before any finishes and that results retain source order

Verification

  • go test ./... (1360 tests)
  • go test -race ./internal/... ./cmd/... (1346 tests)
  • go vet ./...
  • go build ./...
  • gofmt -s -l .
  • git diff --check

Follow-up to #234.

@orian
orian merged commit 46db733 into main Sep 7, 2026
16 checks passed
@orian
orian deleted the feat/locate-resolved-model-search branch September 7, 2026 10:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant