zeek/testing/btest/cluster/websocket
Arne Welzel ca02316671 cluster/websocket: Stop and wait for reply thread during Terminate()
The terminate-while-queueing test added for #4428 failed spuriously
indicating that sometimes WebSocket clients receive code 1000 instead of 1001.
This happens if the ixwebsocket server is shutdown before the reply thread had a
chance to process queued close messages.

Fix by signaling and waiting for the dispatcher's reply thread to terminate
before returning from Terminate().
2025-05-07 12:45:01 +02:00
..
broker btest/cluster/websocket: Move no-subscriptions test 2025-04-25 10:01:23 +00:00
zeromq btest/cluster/websocket: Move no-subscriptions test 2025-04-25 10:01:23 +00:00
bad-event-args.zeek testing/btest: Fix double commented @TEST- lines 2025-05-06 14:06:29 +02:00
bad-subscriptions.zeek testing/btest: Fix double commented @TEST- lines 2025-05-06 14:06:29 +02:00
bad-url.zeek testing/btest: Fix double commented @TEST- lines 2025-05-06 14:06:29 +02:00
cluster-log.zeek testing/btest: Fix double commented @TEST- lines 2025-05-06 14:06:29 +02:00
listen-idempotent.zeek cluster/websocket: Make websocket dispatcher queue size configurable 2025-04-23 14:27:43 +02:00
one-pipelining.zeek testing/btest: Fix double commented @TEST- lines 2025-05-06 14:06:29 +02:00
one.zeek testing/btest: Fix double commented @TEST- lines 2025-05-06 14:06:29 +02:00
terminate-while-queuing.zeek cluster/websocket: Stop and wait for reply thread during Terminate() 2025-05-07 12:45:01 +02:00
three.zeek testing/btest: Fix double commented @TEST- lines 2025-05-06 14:06:29 +02:00
tls-usage-error.zeek cluster/websocket: Implement WebSocket server 2025-03-10 17:07:30 +01:00
tls.zeek testing/btest: Fix double commented @TEST- lines 2025-05-06 14:06:29 +02:00
two-pipelining.zeek testing/btest: Fix double commented @TEST- lines 2025-05-06 14:06:29 +02:00