Name effective defaults in invalid-timeout warning

ce0c3ee→main·

toothbrush·3w ago·1 file·+1 added/-1 removed

Discovery and failover defaults differ, so "using defaults" alone was not actionable when debugging slow-link timeouts.

Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com

Sessions

be0e1af46fffView transcript

[?
Improve Timeout Configuration ClarityClaude Code·Opus 4.8[1m]·1 step](/content/gh/entireio/cli/session/52f42b44-a279-405d-a413-4d922fc42be7#timeline-be0e1af46fff/index.html)

Changes

1

• internal/entireclient/httpclient

• Mtransport.go+1/-1

49 unmodified lines

50
51
52
53
53
54
55
56

49 unmodified lines

}
    secs, err := strconv.Atoi(v)
    if err != nil || secs <= 0 {
        fmt.Fprintf(os.Stderr, "httpclient: ignoring invalid %s=%q, using defaults\n", EnvConnectTimeout, v)
        fmt.Fprintf(os.Stderr, "httpclient: ignoring invalid %s=%q, using defaults (%s failover, %s discovery)\n", EnvConnectTimeout, v, DefaultDialTimeout, DefaultDiscoveryDialTimeout)
        return 0, false
    }
    return time.Duration(secs) * time.Second, true

Minternal/entireclient/httpclient/transport.go+1/-1