Skip to content

Coordinate a server and client measurement without copying addresses from logs #7

Description

@ctfbruce

Problem

Two-sided measurements need a structured listener endpoint and a readiness barrier; a human should not read a server log and manually construct the client arguments.

Proposed change

Add a bounded rendezvous contract and a CLI/SDK helper that starts a server guest, obtains a validated endpoint, starts dependent client guests and cleans up the group.

Acceptance criteria

  • An installed command runs a two-executor echo measurement on an owned local topology.
  • Clients start only after server readiness; readiness timeout, server failure and user cancellation terminate all owned work.
  • Endpoints and results are structured and tied to run identities; no parsing of arbitrary log text or automatic replay after ambiguous submission.

Current evidence

unimplemented requirement. Backlog classification is based on source inspection; this issue does not claim a new runtime reproduction.

Dependencies

  • #2 — Version the HTTP API and publish a machine-readable contract
  • #63 — Persist cancellation intent and expose its acknowledgement state

Validation must use owned local fixtures on supported Linux environments. Record the implementing merge request and relevant test results before closing this issue.


Imported from GitLab issue 6. Originally opened 2026-09-10. Historical GitLab links may require access to the original project.

Activity

  1. added this to the SDK and API milestone on Sep 24, 2026
  2. added
    FeatureA specific missing product behavior.
    P1Core supported-product work to prioritize after the working local alpha.
    SDK and APIVersioned interfaces, usable clients and reproducible examples.
    Source reviewedCurrent source evidence checked; no new runtime reproduction claimed by backlog creation.
    QueuedSelected for upcoming work; implementation has not started and dependencies may remain.
    In progressImplementation is active.
    ReviewImplementation is ready for review and required validation.
    and removed
    QueuedSelected for upcoming work; implementation has not started and dependencies may remain.
    In progressImplementation is active.
    on Sep 24, 2026
  3. ctfbruce commented on Oct 2, 2026

    @ctfbruce
    CollaboratorAuthor

    Completed on main by #354 (merge 4c832c91ae120c02acf8b4f74ced3f8b701ebeff).

    The SDK and installed CLI now coordinate listener readiness and dependent work using owner/run-bound endpoints. Timeout, server failure and cancellation clean up the owned group. The installed two-executor rendezvous and failure-path checks pass; no browser rendezvous UI is claimed.

    Validation: all 16 candidate CI checks passed; the merged tree is identical to that validated candidate.

  4. ctfbruce commented on Oct 7, 2026

    @ctfbruce
    CollaboratorAuthor

    Follow-on grouped measurements are merged in #401 as dc6b55311b3cdd119374e7e3e9bb2cf786037bb1; main CI 37616565917 passed all 16 jobs. The SDK/client support fixed-batch readiness, a shared requested start, grouped result export and cancellation. Dispatcher schema 28 and the optional experiment guest extension are required.

    The console flow is merged in MR 9 as 7d66567b362707d240276bf770d2609f0894f4e9. Main pipeline 517240 passed both automated build/test jobs, including 77 frontend tests. Production deployment remains a separate, unstarted manual job.

    Both merged trees exactly match the candidates exercised in the final owned rehearsal: five distinct executors across four regions, each sending and receiving four direct TCP peer messages (20 directed exchanges), all five successful exits and complete outputs. Browser upload, frozen review, single group submission, participant output inspection and cancellation were exercised. Shared requested-start agreement was verified; the reported 1.027 ms actual-start spread is based on host clocks and does not establish physical clock synchronization or simultaneous execution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    FeatureA specific missing product behavior.P1Core supported-product work to prioritize after the working local alpha.ReviewImplementation is ready for review and required validation.SDK and APIVersioned interfaces, usable clients and reproducible examples.Source reviewedCurrent source evidence checked; no new runtime reproduction claimed by backlog creation.

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions