[BUG] Internal socket and serving-test scopes exclude their callers #37
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/posixd#37
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
Internal socket selection is called from sibling modules but its methods are private to
channel::socket_control. The ordinary-call lifetime work adds the same mismatch for held-source selection. These declarations prevent the callers from composing under Rust privacy rules.Reproduction
Inspect Posixd revision
8df50a15e22a5231edd1cdc9f759d4a798db1f90:src/realm_io/channel/socket_control.rsdeclaressocketandsocket_fromwithout a visibility modifier.channel/named.rscallssocket;channel/wait.rsandchannel/named/publication.rscallsocket_from. These are sibling modules, not descendants ofsocket_control.This report is based on source review. No compiler, unit test, image or CI execution was performed and no diagnostic or exit status is claimed.
Expected and actual behavior
Expected: the internal selectors are accessible within their owning channel implementation, including its sibling submodules, while staying outside the public API.
Actual: the declared private scope excludes those callers. The intended repair is
pub(super)on both methods; it changes no native authority, source selection or runtime effect.Environment and identity
8df50a15e22a5231edd1cdc9f759d4a798db1f90; Integration1871eff2e83ddb5cc3de81132603d4193dbd520a.Evidence and prior checks
The declarations and callers above are direct source evidence. The Rust Reference documents private-module access and parent-scoped visibility. Existing socket, listener, accept and held-call controls consume these paths; compilation and execution remain deferred under the workflow waiver.
A related source audit found that
realm_io::testsaccesses privateRealmIoownership fields declared inrealm_io::serving. Move that existing test module beneathservingwith an explicit source path. This preserves the production field visibility while making the original ownership controls descendants of their owner. No compiler or test execution is claimed.Resolved at source level by signed socket helper visibility and serving ownership test placement. The final Integration selection retains both repairs. Compiler, unit, image and CI execution remain deferred; closure claims source repair only.
Tracking
Whole socket work: #34. Implementation: #5. Phase completion: erix/integration#65.
[BUG] Socket selectors are inaccessible to sibling modulesto [BUG] Internal socket and serving-test scopes exclude their callerserikinkinen referenced this issue from erix/docs2026-10-03 00:22:36 +02:00
erikinkinen referenced this issue2026-10-03 00:22:37 +02:00
erikinkinen referenced this issue from erix/integration2026-10-03 00:22:37 +02:00