[BUG] Restore codec-specific lengths in exact dispatch controls #22
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/vfsd#22
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 V2 cwd-report migration changed three unrelated exact-dispatch controls to expect a 36-byte reply. That length belongs only to the new
/dirreport fixture. The file-read, entry-mutation and metadata controls still use their existing distinct codecs and buffers, so their assertions no longer describe the responses they exercise.Reproduction
Source inspection at Vfsd
2b27ee43c0916737b045a757938ae9440d7d5f9a:src/exact_dispatch/tests.rsagainstedc246ea1ae5829f1e0b0df5a7794a8da103777f.dispatch_uses_endpoint_identity_instead_of_public_handle_ids,exact_entry_mutations_use_only_the_endpoint_bound_target, andexact_entry_metadata_uses_a_selector_free_one_shot_request.No test execution, clean-checkout build or CI reproduction was performed under the current execution deferral.
Expected and actual behavior
Expected: each unchanged fixed codec requires its own complete response extent. Only the new variable cwd report uses its exact encoded length.
Actual: a broad replacement in
b177edd4093c4ed4ed42444d1615899f8439d06fapplied the cwd fixture length to three unrelated assertions. This is a source-confirmed test regression; no runtime failure or production authority defect is alleged.Environment and identity
2b27ee43c0916737b045a757938ae9440d7d5f9a; the regression was introduced inb177edd4093c4ed4ed42444d1615899f8439d06f. Integration runtime selection was not changed by these commits.edc246ea1ae5829f1e0b0df5a7794a8da103777fretain their own buffer lengths; no execution success is claimed.Evidence and prior checks
The published diff changes the same assertion in four controls, while only
exact_path_read_is_repeatable_only_on_the_job_cwd_endpointchanged wire format. Restore the three unrelated assertions and retain the V2 getter's variable-length control. Execution remains deferred.Tracking
Related migration: optional native cwd descriptions and the component review.
Acceptance: restore the original file-read, mutation and metadata response extents; preserve the V2 cwd reply length; publish the source correction and report validation truthfully.
Source resolution
Signed correction 0753e4be restores the three unchanged codec-specific response extents and preserves the V2 cwd getter's 36-byte fixture assertion. The source fix is complete. Formatting was applied through stdin; tests, builds, checks and CI observation remain deferred, so this closure records source completion without claiming an execution pass.
erikinkinen referenced this issue2026-10-01 17:13:14 +02:00
erikinkinen referenced this issue from erix/integration2026-10-01 17:13:16 +02:00
erikinkinen referenced this issue2026-10-01 17:13:17 +02:00
erikinkinen referenced this issue from erix/docs2026-10-01 17:13:17 +02:00
erikinkinen referenced this issue from erix/integration2026-10-01 17:13:18 +02:00
erikinkinen referenced this issue from erix/posixd2026-10-01 17:13:19 +02:00
erikinkinen referenced this issue from erix/lib-ipc2026-10-01 17:13:19 +02:00
erikinkinen referenced this issue from erix/ramfsd2026-10-01 17:13:19 +02:00
erikinkinen referenced this issue from erix/e2fsd2026-10-01 17:13:20 +02:00
erikinkinen referenced this issue from erix/fatd2026-10-01 17:13:20 +02:00
erikinkinen referenced this issue from erix/exsh2026-10-01 17:13:21 +02:00
erikinkinen referenced this issue from erix/coreutils2026-10-01 17:13:21 +02:00