[BUG] Native man cannot resolve the workspace-exhaustion helper #6
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/coreutils#6
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
The native manual reader does not compile because two capacity-refusal paths
refer to a helper that is outside their module scope. This blocks Coreutils
runtime builds, including image consumers.
Reproduction
Build Coreutils at
726df3c406d9c7226e517c32d594993921564a5awith the nativeruntime enabled. The hosted all-target/all-feature unit and Clippy commands,
and the freestanding runtime check and Clippy commands, each fail with E0425.
The unresolved calls are in
src/runtime/execute/manual.rs.Expected and actual behavior
Empty caller-owned read or selector storage should return the existing status 1
and workspace diagnostic before requesting file authority. Compilation instead
fails because
super::workspace_exhaustedis not defined in the common executemodule; the existing implementations live in sibling modules.
Environment and identity
726df3c406d9c7226e517c32d594993921564a5a.manual-reader revision is established.
Evidence and prior checks
Four compiler commands fail at the same two unresolved references. The separate
packer, script, documentation and formatting results do not establish a runtime
build pass.
The shared helper repair
moves the existing diagnostic into the common scope and removes its duplicates.
A driver regression
covers both pre-effect capacity refusals and buffer clearing.
Tracking
Related to native man and
Coreutils PR2.
Fixed in 8f976de5, with both pre-effect refusal controls in 6dca9fb9. All 185 Rust tests and the affected hosted/freestanding strict checks pass. Both capacity refusals acquire no file authority, consume no input and clear their buffers. The original compiler failures remain recorded.