mirror of
https://github.com/paperclipai/paperclip.git
synced 2026-10-08 11:13:44 +02:00
The test opened a duplex channel with data scripted to arrive right after the open reply. Under load, the host could process that data notification before the open reply's own continuation bound the route. The ceiling rejection then raced the bind, and the open call itself failed with DUPLEX_CHANNEL_OPEN_FAILED instead of the intended post-bind rejection. Open the channel with no scripted data, then write one byte after the open call resolves. The write is strictly post-bind, so the rejection is always a genuine post-bind event. Also name the reservation that rejects. The host makes two reservations for the write. The raw payload byte fits the ceiling. The serialized host-to-worker frame does not. The test name and the comments now describe that path. Co-authored-by: Paperclip <noreply@paperclip.ing>