zeek/testing/btest/Baseline/cluster.websocket.metadata
Arne Welzel 9a7678f15a cluster/Backend: Fallback to current network time when current event has not timestamp
When a WebSocket client sends an event to Zeek without explicit network
timestamp metadata, Zeek would use -1.0 as a timestamp for any events
published while handling this event. Instead, it seems far more sensible
to use the current network time in that scenario.
2025-08-20 19:56:50 +02:00
..
..client-metadata-from-client..stderr cluster/serializer/broker: Do not send empty metadata vectors around 2025-08-20 19:55:38 +02:00
..client-metadata-from-client.out cluster/serializer/broker: Do not send empty metadata vectors around 2025-08-20 19:55:38 +02:00
..client-metadata..stderr cluster/serializer/broker: Do not send empty metadata vectors around 2025-08-20 19:55:38 +02:00
..client-metadata.out cluster/Backend: Fallback to current network time when current event has not timestamp 2025-08-20 19:56:50 +02:00
..client-no-metadata..stderr cluster/serializer/broker: Do not send empty metadata vectors around 2025-08-20 19:55:38 +02:00
..client-no-metadata.out cluster/serializer/broker: Do not send empty metadata vectors around 2025-08-20 19:55:38 +02:00
..manager-metadata-from-client..stderr cluster/serializer/broker: Do not send empty metadata vectors around 2025-08-20 19:55:38 +02:00
..manager-metadata-from-client.out cluster/serializer/broker: Do not send empty metadata vectors around 2025-08-20 19:55:38 +02:00
..manager-metadata..stderr cluster/serializer/broker: Do not send empty metadata vectors around 2025-08-20 19:55:38 +02:00
..manager-metadata.out cluster/serializer/broker: Do not send empty metadata vectors around 2025-08-20 19:55:38 +02:00
..manager-no-metadata..stderr cluster/serializer/broker: Do not send empty metadata vectors around 2025-08-20 19:55:38 +02:00
..manager-no-metadata.out cluster/serializer/broker: Do not send empty metadata vectors around 2025-08-20 19:55:38 +02:00