Skip to content

fix(tcp): User Timeout option loses its granularity bit on rebuild #1219

Closed

Description

@JarryShaw

Describe the bug
The reader converts the value to a timedelta (transport/tcp.py:1391-1399), and the maker then chooses G by size (:2602-2603).

To Reproduce
1c048005 (5 minutes, G=1) rebuilds as 1c04012c (300 seconds, G=0).

Expected behavior
The parsed granularity is stored in Data_UserTimeout and the maker honours it.

Found by the transport round-trip audit (#1202). I re-ran the repro on main at 630f0a581.

Activity

  1. added
    fixPull requests that fix a defect (fix: subject prefix)
    pendingAccepted and unstarted - nobody is on it and nothing blocks it
    on Oct 7, 2026
  2. JarryShaw commented on Oct 7, 2026

    @JarryShaw
    OwnerAuthor

    Blocked until the MPTCP PR for #1212–#1217/#1220 merges, because both edit transport/tcp.py and its schema and data modules.

  3. added
    blockedDeferred pending another issue or decision; see the last comment for what unblocks it
    and removed
    pendingAccepted and unstarted - nobody is on it and nothing blocks it
    on Oct 7, 2026
  4. JarryShaw commented on Oct 7, 2026

    @JarryShaw
    OwnerAuthor

    Unblocked: #1254 merged at 19:08Z, so the file conflict is gone. Back to pending until a worker picks it up.

  5. added
    pendingAccepted and unstarted - nobody is on it and nothing blocks it
    wipWork in flight - a covering PR is open or an agent is actively on it
    and removed
    blockedDeferred pending another issue or decision; see the last comment for what unblocks it
    pendingAccepted and unstarted - nobody is on it and nothing blocks it
    on Oct 7, 2026
  6. removed
    wipWork in flight - a covering PR is open or an agent is actively on it
    on Oct 7, 2026
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

    fixPull requests that fix a defect (fix: subject prefix)

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions