Repository navigation
feat(core): add a per-project outside-repo artifact landing #9776
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 2 commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
94f4457
feat(core): add a per-project outside-repo artifact landing
wenshao aab0887
fix(core): validate every component of the fallback landing path
wenshao ed40014
fix(core): close audit landing adoption escapes (#9776)
qwen-code-ci-bot 3183d34
fix(core): close audit landing race seams with re-validation (#9776)
qwen-code-ci-bot e70d160
Merge branch 'main' into feat/audit-fallback-dir
qwen-code-dev-bot 803db8e
Merge branch 'main' into feat/audit-fallback-dir
qwen-code-dev-bot ca7f354
fix(core): harden audit fallback validation per review (#9776)
qwen-code-dev-bot 2e6bd8d
Merge branch 'main' into feat/audit-fallback-dir
wenshao da4d45a
fix(core): re-check landing contents in pre-return re-validation (#9776)
qwen-code-dev-bot 3a2779a
Merge branch 'main' into feat/audit-fallback-dir
wenshao 863132f
Merge branch 'feat/audit-fallback-dir' of https://github.com/QwenLM/q…
qwen-code-dev-bot 0859695
fix(core): drive landing content check from fresh per-entry lstat (#9…
qwen-code-dev-bot fe77863
fix(core): re-lstat audit landing after follow-based validation steps…
qwen-code-dev-bot 5a826b1
Merge branch 'main' into feat/audit-fallback-dir
wenshao 71a6928
fix(core): fold case in audit landing containment on case-insensitive…
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.
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.
Declined as proposed, with the limitation documented instead. Refusing adoption of pre-existing components on win32 would also refuse this tool's OWN landings from previous runs — the landing is deliberately reused across runs (the report and its sidecar are the durable artifacts), and on Windows nothing distinguishes self-created from planted. The effect would be every second
/auditrun per project failing forever with "remove it and re-run", breaking the reuse contract this same file argues for. Instead the mode-repair comment now states the win32 truth plainly: an adopted component keeps whatever DACL it had, since Node exposes no portable ACL enforcement. If a maintainer wants a stronger win32 guarantee anyway, a creation marker (written when this tool creates a component, required for adoption) could distinguish self-created landings — say the word and I will implement it.中文说明
按提议的方案予以拒绝,改为如实记录该限制。在 win32 上拒绝采纳已存在组件,会同时拒绝本工具此前运行自建的落点——落点是刻意跨运行复用的(报告及其 sidecar 是持久产物),而 Windows 上无法区分自建与植入。其后果将是每个项目每隔一次
/audit运行就永远失败并提示「移除后重跑」,打破同一文件为之辩护的复用契约。因此改为在模式修复注释中如实写明 win32 现状:已存在组件保留其既有 DACL,因为 Node 没有可移植的 ACL 强制。若维护者仍希望更强的 win32 保证,可以用创建标记(本工具创建组件时写入、采纳时要求存在)来区分自建落点——如有指示,乐意实现。