[BUG] Restore codec-specific lengths in exact dispatch controls #22

Closed
opened 2026-10-01 17:11:41 +02:00 by erikinkinen · 0 comments
Owner

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 /dir report 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:

  1. Compare src/exact_dispatch/tests.rs against edc246ea1ae5829f1e0b0df5a7794a8da103777f.
  2. Inspect dispatch_uses_endpoint_identity_instead_of_public_handle_ids, exact_entry_mutations_use_only_the_endpoint_bound_target, and exact_entry_metadata_uses_a_selector_free_one_shot_request.
  3. Each still allocates and parses its original fixed codec response, but now compares the reported length to 36 instead of the corresponding complete buffer extent.

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 b177edd4093c4ed4ed42444d1615899f8439d06f applied 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

  • Component repository/revision and Integration source graph: Vfsd 2b27ee43c0916737b045a757938ae9440d7d5f9a; the regression was introduced in b177edd4093c4ed4ed42444d1615899f8439d06f. Integration runtime selection was not changed by these commits.
  • Image profile, digest and build/runtime configuration: no image was built or executed for this observation.
  • Hardware or VM, architecture, firmware and toolchain versions: not applicable to source inspection.
  • Input/session route and granted authority relevant to reproduction: existing native resolver and exact-dispatch test fixtures; no additional authority.
  • Last known working revision, if known: the corresponding source assertions in edc246ea1ae5829f1e0b0df5a7794a8da103777f retain 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_endpoint changed 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.

## 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 `/dir` report 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`: 1. Compare `src/exact_dispatch/tests.rs` against `edc246ea1ae5829f1e0b0df5a7794a8da103777f`. 2. Inspect `dispatch_uses_endpoint_identity_instead_of_public_handle_ids`, `exact_entry_mutations_use_only_the_endpoint_bound_target`, and `exact_entry_metadata_uses_a_selector_free_one_shot_request`. 3. Each still allocates and parses its original fixed codec response, but now compares the reported length to 36 instead of the corresponding complete buffer extent. 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 `b177edd4093c4ed4ed42444d1615899f8439d06f` applied 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 - Component repository/revision and Integration source graph: Vfsd `2b27ee43c0916737b045a757938ae9440d7d5f9a`; the regression was introduced in `b177edd4093c4ed4ed42444d1615899f8439d06f`. Integration runtime selection was not changed by these commits. - Image profile, digest and build/runtime configuration: no image was built or executed for this observation. - Hardware or VM, architecture, firmware and toolchain versions: not applicable to source inspection. - Input/session route and granted authority relevant to reproduction: existing native resolver and exact-dispatch test fixtures; no additional authority. - Last known working revision, if known: the corresponding source assertions in `edc246ea1ae5829f1e0b0df5a7794a8da103777f` retain 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_endpoint` changed 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](https://git.erikinkinen.fi/erix/vfsd/issues/16) and [the component review](https://git.erikinkinen.fi/erix/vfsd/pulls/3). 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](https://git.erikinkinen.fi/erix/vfsd/commit/0753e4bebad5fb2b08c44087a7ba4013eea1b166) 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 added this to the Alpha 1 milestone 2026-10-30 09:35:18 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erix/vfsd#22
No description provided.