Repository navigation
fix: v2.0.8 gate reliability and approved OpenMDW-1.1 admission - #14
Merged
Merged
Conversation
added 4 commits
October 19, 2026 15:04
lvj-repox
marked this pull request as ready for review
October 19, 2026 07:21
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.
v2.0.8 candidate validation — 2026-10-19
Implementation tested:
56fa851906c937a309c4d67790177d293732371a.PR: #14
Results
tests/pr_gate_self_test.pyon nmz1; also hosted CItests/real_tools_integration.pyon nmz4, all 30 casesbash -n scripts/prepare-python.shHosted CI evidence: https://github.com/HYGON-AI/quality-gate/actions/runs/39215002651
“Expected outcomes” includes intentionally blocked findings (exit 2), operational failures (exit 1) and clean/advisory passes (exit 0). Tests do not redefine expected errors as successes in production.
Historical replays
Only native Code compliance was replayed against existing checkouts, without changing their files, refs or configuration. All writeable test outputs live in separate temporary directories; target code is never executed.
463e2f4536d2fe829947b5246b26f972cf78a728, heada6ca2d3bcf93def95354eccf1eebd0a305edf001. Initial fixed replay on nmz4: 0.132s, peak RSS 29,200 KiB, exit 0. Original stable attempt 4 grew to about 538 GiB by four minutes before cancellation. The 49 changed files include only two non-deleted files; the large Python file triggered duplicate branch-value growth, not model execution.acf085724329a8c07556709324cb757ce7046fbd, headd1591e5c528a017e14f2a3bf66bd4a9d9acf90cf. Fixed replay on nmz6: 0.038s, peak RSS 19,532 KiB, exit 0. Gitlinks no longer attempt to read a foreign commit as a source blob.Negative controls and additional defects
MemoryErrorexplicitly fail. The old orchestrator could replaceMemoryErrorwith an empty status detail and accidentally return Passed; this is covered separately.ruff.tomlper-file F823 ignores, inlinenoqa, and.gitattributes -diffcannot hide the synthetic new F823 defect. Textconv suppression is separately unit tested.Release boundary
At validation completion this remains a candidate: required independent approval, merge and post-merge checks precede the release/tag update. No immutable tag, stable pointer, runner-group permission, system Python or node configuration was changed by these tests. GitHub status and final tested commit must be rechecked immediately before publishing.