Repository navigation
fix: harden FPM onboarding collection and prediction #379
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
Arsene12358
wants to merge
14
commits into
main
Choose a base branch
from
fix/fpm-finalization-followup-20261003
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
102d6dc
fix: distinguish FPM worker probe sidecars from rank artifacts
Arsene12358 eadc40f
fix: wait for native FPM artifact finalization
Arsene12358 8bc44d6
fix: propagate Slurm worker failures in completion order
Arsene12358 5bac3f5
fix: bind runtime memory evidence to independent collection phases
Arsene12358 4c72b33
fix: reject conflicting readiness plan inputs
Arsene12358 0f25427
fix: review AISimulate source revisions separately from model identity
Arsene12358 b96b560
fix: review archived collection controls for memory compatibility
Arsene12358 5ed5092
fix: add KV-first fallback for direct FPM prefill
Arsene12358 3998c92
Merge main into FPM onboarding follow-up
Arsene12358 3bca288
Merge runtime evidence linkage into FPM onboarding follow-up
Arsene12358 57cc3fe
Merge KV-first interpolation into FPM onboarding follow-up
Arsene12358 c869bb1
fix: preserve readiness reports for unavailable runtime indexes
Arsene12358 75b00be
fix: qualify readiness errors against selected evidence
Arsene12358 20e3eb9
fix: load aggregated FPM full-grid medians
Arsene12358 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎯 Functional Correctness | 🟠 Major | 🏗️ Heavy lift
The KV-first fallback changes direct-prefill answers that were previously unsupported. The required golden and parity evidence for those answers is missing.
Before this change, a query without a token-first KV bracket returned an error. Line 635 now returns an interpolated latency for some of these queries. The path instructions treat a change in interpolation or fallback ordering as a change in numerical behavior. The PR reports parity runs, but they ran before the final Python fix. The PR also does not show an append-only pinned parity case or an explained golden diff for the newly supported queries. The PR reports artificial cross-graph/eager cases with 24.82–60.98% error. Those are cases where the token axis crosses a capture-regime boundary. Decode stays inside one inferred regime (
direct_decode_rungs). The KV-first token bracket has no regime gate, so it can blend measurements taken from different execution graphs.Required changes:
As per path instructions: "Require an explained before/after golden diff or hand-derived oracle evidence for changed answers."
🤖 Prompt for AI Agents
Source: Path instructions