-
Notifications
You must be signed in to change notification settings - Fork 255
[Klaud Cold] Enact the August 3, 2026 scenario and precision deprecations / 执行 2026 年 8 月 3 日场景与精度下线 #2493
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
Merged
Merged
[Klaud Cold] Enact the August 3, 2026 scenario and precision deprecations / 执行 2026 年 8 月 3 日场景与精度下线 #2493
Changes from all commits
Commits
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
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
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
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
2 changes: 1 addition & 1 deletion
2
..._node/minimaxm3_fp4_mi355x_atom-disagg.sh → ...cated/minimaxm3_fp4_mi355x_atom-disagg.sh
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
2 changes: 1 addition & 1 deletion
2
..._node/minimaxm3_fp4_mi355x_vllm-disagg.sh → ...cated/minimaxm3_fp4_mi355x_vllm-disagg.sh
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
2 changes: 1 addition & 1 deletion
2
..._node/minimaxm3_fp8_mi355x_atom-disagg.sh → ...cated/minimaxm3_fp8_mi355x_atom-disagg.sh
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
2 changes: 1 addition & 1 deletion
2
..._node/minimaxm3_fp8_mi355x_vllm-disagg.sh → ...cated/minimaxm3_fp8_mi355x_vllm-disagg.sh
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
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
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
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
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
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
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
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
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
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
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
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
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
2 changes: 1 addition & 1 deletion
2
...ixed_seq_len/minimaxm3_fp4_mi355x_atom.sh → ...n/deprecated/minimaxm3_fp4_mi355x_atom.sh
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
2 changes: 1 addition & 1 deletion
2
..._seq_len/minimaxm3_fp4_mi355x_atom_mtp.sh → ...precated/minimaxm3_fp4_mi355x_atom_mtp.sh
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
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
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
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
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
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.
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.
🟡 The self-referential PR link uses a literal
PRNUMplaceholder instead of2493in both MODELS.md (lines 15, 56, 57, 61) and the mirrored lines in MODELS_zh.md, producing 8 broken/pull/PRNUMlinks (404) in the docs that are this PR's own deliverable. Fix with a simple find-and-replace ofPRNUM→2493in both files.Extended reasoning...
This PR's whole purpose is to record the enactment of the August 3, 2026 deprecation notice and link back to the PR that did it. Four places in
MODELS.md(lines 15, 56, 57, 61) and the four mirrored lines inMODELS_zh.mdwrite[#PRNUM](https://github.com/SemiAnalysisAI/InferenceX/pull/PRNUM)where the actual PR number, 2493, should be. This is a leftover template placeholder — the author correctly filled in the real numbers for every other PR reference on those lines (e.g.#2268,#1724,#734), but couldn't have known this PR's own number ahead of time and never went back to substitute it once the PR was opened.I verified this against the actual committed file content, not the PR diff view:
grep -n PRNUM MODELS.md MODELS_zh.mdon the current working tree returns all 8 occurrences, andgit show HEAD:MODELS.mdconfirms the same text is present in the commit that shipped this change (5b5606e, "docs(MODELS): record the August 3, 2026 deprecations as enacted"). The diff shown during review substitutes the placeholder with#2493for display purposes, which is why it can look already-fixed there — but the file actually on disk/in HEAD still has the raw placeholder.Concretely, anyone who clicks the "Enacted on 2026-08-04 in #PRNUM" link at MODELS.md:15, or either of the "no active config as of 2026-08-04 (#PRNUM)" callouts at lines 56-57, or the "Agentic coding (removed 2026-08-04, #PRNUM)" note at line 61, lands on
https://github.com/SemiAnalysisAI/InferenceX/pull/PRNUM, which is not a valid PR number and 404s. Same for the four mirrored Chinese-language lines in MODELS_zh.md. Since the whole point of these notes is to let a future reader jump straight to the PR that performed the archival/removal, a dead link defeats that purpose, even though it doesn't break any code, CI, or benchmark behavior.Fix is mechanical: replace
PRNUMwith2493in both files (8 substitutions total, matching the#2493display already shown in the PR's own diff view). Since this is a documentation-only defect with no functional or CI impact, I'm marking it a nit rather than a blocking issue — but it should be fixed before merge since it's trivial and the whole point of the change is to leave working self-referential links.