-
Notifications
You must be signed in to change notification settings - Fork 3k
feat(review): add a --topology minimal single-pass A/B arm #9919
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
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
395a1fc
feat(review): add a --topology minimal single-pass A/B arm
wenshao 0817a7c
Merge remote-tracking branch 'origin/main' into feat/review-minimal-t…
qwen-code-dev-bot c793f2d
fix(review): gate --resume under minimal topology and add its complet…
qwen-code-dev-bot cba3a29
fix(review): align --topology minimal with Step 8, Step 6 tips, and t…
qwen-code-dev-bot dafe7a1
fix(review): name the real blocker in the minimal write refusal and e…
qwen-code-dev-bot dc5a5cf
Merge remote-tracking branch 'origin/main' into feat/review-minimal-t…
qwen-code-dev-bot 2fa7756
fix(review): give the minimal write refusal its own advice arm and pi…
qwen-code-dev-bot 7e7f14a
chore(review): drop stray escapes from the minimal-topology test comm…
qwen-code-dev-bot 11cf00c
fix(review): classify write-refusal advice structurally and label min…
qwen-code-dev-bot 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
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.
[Suggestion] This new topology refusal is a third refusal class, but its only shape-sensitive consumer — the advice dispatch at
submit.ts:746(auth.why.includes('--commentwas')) — still knows only two classes. The refusal string contains no such substring, so the dispatch selects the second arm, whose preamble "Nothing recorded authorises binding this target" is false for this class — the record DID name the target and bound every axis (that is why it reached the topology block at all) — and whose remedy "a review invoked naming it" re-refuses while the topology is kept: the futile-retry loop the dispatch's own comment block exists to prevent.Aggravating: that arm's other remedy — "
--user-authorizedafter the user has asked" — mechanically succeeds against the same record (fast pathok: trueobserved at HEAD), so the advice appended to this refusal actively points at the bypass of that very refusal.Fix in
submit.ts— a third dispatch arm keyed on the topology marker, checked before the existing branch, whose advice restates the refusal's own remedy (re-run without--topology minimal) and does not offer--user-authorized.中文说明
这个新的 topology 拒绝是第三个拒绝类别,但它唯一的「按措辞分流」的消费者——
submit.ts:746的建议分发(auth.why.includes('--commentwas'))——仍然只认识两个类别。该拒绝字符串不含该子串,因此分发落入第二个分支:其前言「没有任何记录授权绑定此目标」对本类别是错误的——记录确实指名了目标并在各轴上完成绑定(正因如此才走到 topology 块)——其补救「用指名该目标的评审重跑」在保留 topology 时会再次被拒:正是分发自己的注释块所要防止的「徒劳重试」循环。更糟的是:该分支的另一个补救——「用户已要求后用
--user-authorized」——对同一条记录在机制上会成功(已在 HEAD 观察到快速路径返回ok: true),因此附加在这条拒绝之后的建议,恰恰指向了绕过该拒绝本身的通路。请在
submit.ts中修复:新增以 topology 标记为键的第三个分发分支,置于既有分支之前检查,其建议复述拒绝自身的补救(去掉--topology minimal重跑),且不提供--user-authorized。— qwen3.8-max via Qwen Code /review (v0.22.0)