Vitor PamplonaandClaude Opus 5 054c665696 test: pin that live websockets hold their OkHttp dispatcher slot forever ...

The app dials ~190 relays in one burst from RelayPool.connect() and spikes to
~640 threads, so capping the relay client's Dispatcher.maxRequests looks like a
one-line throttle.

It is not. Against a real relay, maxRequests=4 with 20 dials opens exactly 4;
the other 16 queue forever and never fail, so nothing surfaces the stall.
Setting maxRequests=N would cap the app at N relays permanently.

Pins the behaviour so the knob is not reached for again. Throttling has to
happen above OkHttp, in RelayPool, where a settled dial can release its permit.

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

2026-08-14 11:26:01 -04:00

..

main/kotlin/com/vitorpamplona/geode

Return the walk's outcome instead of signalling a drain by callback

2026-08-09 05:25:06 +00:00

test/kotlin/com/vitorpamplona/geode

test: pin that live websockets hold their OkHttp dispatcher slot forever

2026-08-14 11:26:01 -04:00

testFixtures/kotlin/com/vitorpamplona/geode

Suspend the incoming-message chain down to SubscriptionListener.onEvent

2026-08-05 12:45:02 -04:00