Merge Dev - Lineage-wide run inspection in the CLI#161
Merged
Merged
Conversation
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.
Lineage-wide run inspection in the CLI
The
weco runread commands were single-run scoped — once a run had beenderived, an agent (or user) couldn't see the global best, the derived branches, or the tree the way the dashboard does. This adds lineage-aware inspection on top of the existing per-run commands. No backend changes — the lineage endpoints already exist.New -
weco run overview <run-id>The full lineage picture in one call (dashboard parity). Pass any run ID in the lineage; returns the aggregate (status, global best metric, summed steps, member counts), the global best node across all runs, the member tree (each with its
derived_frombranch point, per-member best, and children), and theglobal_step-ordered node list. Supports--plot(lineage-wide trajectory) and--include-code.WecoClient.list_lineage_nodes()(GET /lineages/{id}/nodes) and shared helpersresolve_lineage_id/fetch_lineage/fetch_lineage_nodes.Changed -
status/resultsgain--lineageto scope across all derived runs.Per-run stays the default - fully backward compatible. Lineage rows are labelled by
global_stepwithrun:stepsecondary, matching the dashboard.show/diff:--step bestnow resolves the lineage-best node - the same onederive --from-step bestbranches from — and surfaces itsrun_idwhen it lives in a different sub-run. Added--step run-bestfor the best within just the queried run. (Fixes the prior inconsistency wherebestmeant run-best here but lineage-best inderive.)