[anneal] Align root-manifest validation across the updater and standalone auditor
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- build-system, testing
Research direction
Read ci/update_root_manifest.py around lines 32–55 and trusted/audit/src/lib.rs around lines 1032–1057 to compare accepted checksum markers. Check the manifest absence review thread and identify which entry points require locked inputs; the hosted workflow already requires the file. Done means updater and auditor accept the same manifest formats and required entry points fail when the manifest is absent.
Written by the indexing model from the issue text.
Description
The root-manifest updater preserves both GNU checksum mode markers,
while the Rust auditor recognizes only the two-space text-mode
separator. A binary-mode entry accepted by the updater can therefore
fail when the standalone auditor reads the same manifest.
The standalone auditor also accepts an absent manifest. Decide which
entry points require the locked inputs and make absence fail for those
entry points. The hosted workflow already requires the file.
Manifest absence review thread
This is a follow-up to importing the auditor at the exact source
revision. The updater and auditor should agree on the accepted
manifest format.
Updater at c131b32 · Auditor at c131b32 · Migration review thread
Authored by an AI agent acting on joshlf's behalf.
- Dominant language
- Rust
- Stars
- 2.6k
- Forks
- 194
- Avg merge
- 18h 15m
- Merged PRs (30d)
- 14
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from google/zerocopy
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Features to support optional defmt for the byteorder typesPossibly taken A pull request linked to this issue is open or already merged. Opencustomer-request
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
google/zerocopy#3914 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
google/zerocopy#3766 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
swc-project/swc-next-issues#533 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
eandualem/agent-interface#290 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day