Claude fbccc6087d Keep lazy connections enabled in the agent-network e2e harness ...

Revert the NB_LAZY_CONN=false override on the harness client and proxy
containers: with the DNS-time lazy-connection warm-up in place, the
harness resolves the endpoint first, which wakes the proxy peer before
WaitProxyPeer polls for it. Running the suite with lazy connections on
is the point — it exercises the warm-up path end to end.

2026-07-22 04:51:57 +00:00

..

agentnetwork.go

[management,client] 0.74.5 branch sync (#6769)

2026-07-14 21:22:40 +02:00

bootstrap.go

[management,proxy,client] 0.74.0 version (#6563)

2026-07-01 12:45:14 +02:00

cert.go

[management,proxy,client] 0.74.0 version (#6563)

2026-07-01 12:45:14 +02:00

client.go

Keep lazy connections enabled in the agent-network e2e harness

2026-07-22 04:51:57 +00:00

combined.go

[management,proxy,client] 0.74.0 version (#6563)

2026-07-01 12:45:14 +02:00

config.go

[management,proxy,client] 0.74.0 version (#6563)

2026-07-01 12:45:14 +02:00

doc.go

[management,proxy,client] 0.74.0 version (#6563)

2026-07-01 12:45:14 +02:00

Dockerfile.client

[management,proxy,client] 0.74.0 version (#6563)

2026-07-01 12:45:14 +02:00

paths.go

[management,proxy,client] 0.74.0 version (#6563)

2026-07-01 12:45:14 +02:00

proxy.go

Keep lazy connections enabled in the agent-network e2e harness

2026-07-22 04:51:57 +00:00

upstream.go

[management,proxy] Add per-provider skip_tls_verification for agent-network (#6630)

2026-07-01 20:43:15 +02:00

vllm.go

[management] Add vLLM e2e test (#6649)

2026-07-02 15:36:51 +02:00