macOS contributor gates: Messaging config tests fail under the symlinked macOS temporary directory
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 83/100
Research direction
Start with the three failing tests in crates/registry-messaging/src/config.rs around lines 1798 and 1817, then compare how other products' config tests handle temporary directories. Reproduce the failures on macOS or inspect the scheduled "macOS contributor gates" workflow. Done when the tests use a canonicalized fixture path and pass while preserving the loader's symlink refusal behavior.
Written by the indexing model from the issue text.
Description
The scheduled "macOS contributor gates" workflow has failed on every run since at least 15 November (the runs for 7f47a330f6, a8e5e49efe, fd2a888614 and 4be684f206). The 19 November run, which tested 4be684f206, failed in "Direct Cargo binaries and database-free gates": three registry-messaging config tests fail on macOS.
config::tests::runtime_loader_accepts_an_owner_writable_file_in_a_private_directory(crates/registry-messaging/src/config.rs:1817): the loader refuses the file withplatform.runtime-config.unsafe-file, "the runtime configuration path must not pass through" a symlink. The temporary directory is under/var/folders/..., and/varis a symlink to/private/varon macOS.config::tests::runtime_loader_refuses_a_group_writable_ancestorandconfig::tests::runtime_loader_refuses_a_group_writable_file(config.rs:1798): the refusal arrives, but for the symlinked path, so the assertion that the message mentions "owned by root or the runtime user" fails.
Likely cause
The tests build their fixtures under the default temporary directory without canonicalising it. Linux has no symlink there, so CI on Linux passes. The loader's refusal of symlinked paths is intended. The tests probably need to canonicalise the temporary directory, as other products' config tests do.
Not checked
I did not check whether the earlier failing runs failed for the same reason. They failed in the same job.
- Dominant language
- Rust
- Stars
- 2
- Forks
- 0
- Avg merge
- 9h 48m
- Merged PRs (30d)
- 151
Getting set up
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 registrystack/registry-stack
-
area:breg enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
registrystack/registry-stack#2765 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
registrystack/registry-stack#2761 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
registrystack/registry-stack#2743 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
registrystack/registry-stack#2706 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
registrystack/registry-stack#2698 ·
Maintainers usually reply within 1 day
All issues in registrystack/registry-stack
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
AstrBotDevs/AstrBot-desktop#197 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
stackabletech/airflow-operator#898 ·
Maintainers usually reply within 1 day
-
2 advisory ignore entries no longer match anything (`bytes`, `time` already patched in `Cargo.lock`)Possibly taken @zyl71 claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100