Refuse a missing [nodes] directory with a clean message instead of the cargo metadata leak #245

Closed
opened 2026-07-12 17:58:54 +02:00 by Brummel · 0 comments
Owner

Friction (fieldtest cycle-241, 2026-07-12, engine at 72c0b8a)

An Aura.toml [nodes] pointer at a missing directory refuses with the pointer context wrapping a raw toolchain error:

aura: node crate at `../nope` (from [nodes] in Aura.toml): cargo metadata failed: error: failed to load manifest ... (os error 2)

The pointer prefix (#241) is right; the inner cargo metadata + os error 2 tail is noise for what is simply a nonexistent directory. A pre-check on the pointer target (node crate directory does not exist (from [nodes] in Aura.toml)) would say exactly that; the cargo-metadata wrap stays for genuinely broken crates (dir exists, no cdylib manifest).

## Friction (fieldtest cycle-241, 2026-07-12, engine at 72c0b8a) An `Aura.toml` `[nodes]` pointer at a missing directory refuses with the pointer context wrapping a raw toolchain error: aura: node crate at `../nope` (from [nodes] in Aura.toml): cargo metadata failed: error: failed to load manifest ... (os error 2) The pointer prefix (#241) is right; the inner `cargo metadata` + `os error 2` tail is noise for what is simply a nonexistent directory. A pre-check on the pointer target (`node crate directory `<path>` does not exist (from [nodes] in Aura.toml)`) would say exactly that; the cargo-metadata wrap stays for genuinely broken crates (dir exists, no cdylib manifest).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Brummel/Aura#245