Skip to content

Bug: When default_max_path_idle_timeout is set to a lower value than connection idle timeout then WARN logs are emitted for connections to unreachable targets #656

@Frando

Description

@Frando
  • Iroh sets default_path_max_idle_timeout to 15s, and leaves the connection idle timeout at 30s
  • When you connect to an unreachable target, noq keeps resending the initial into the void (correct
  • After 15s we get a WARN log:
2026-05-15T11:27:01.511149Z  WARN connect{me=5621ed0fb1 alpn=n0/iroh/transfer/example/1 remote=f2a26551fb}:drive{id=4}:timer_fired{scope="path" path_id=0 timer=PathIdle}: noq_proto::connection: failed closing path err=MultipathNotNegotiated

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status
    🚑 Needs Triage

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions