4 commits

Author	SHA1	Message	Date
Arne Welzel	f57a1263d4	cluster/serializer/broker: Do not special case Broker::Data anymore ... The previous approach ignored the fact that nested / inner values might also be Broker::Data values. I'm not super sure about the validity of the test, because it's essentially demonstrating any-nesting, but it's not leading to extra Broker::Data encoding.	2025-08-17 16:56:20 +02:00
Arne Welzel	3ec3205074	btest/cluster/generic/publish-any: Apply Christian's fix from broker/publish-any	2025-05-07 17:18:01 +02:00
Arne Welzel	21e33fdcd9	btest/cluster: Bump timeouts to 30 seconds ... ZAM startup may take a long time, particularly in CI environments, so bump it up from 10 to 30 seconds.	2024-12-13 18:28:43 +01:00
Arne Welzel	d9a74cf32d	cluster: Fix Cluster::publish() of Broker::Data ... The broker serializer leverages the existing data_to_val() function. During unserialization, if the destination type is any, the logic simply wraps the broker::data value into a Broker::Data record. Therefore, events with any parameters are currently exposed to the Broker::Data type. There is a bigger issue in that re-publishing such Broker::Data instances would encode them as a normal record. Explicitly prevent this by serializing the contained data value directly instead, similar to what Broker already did when publishing a record.	2024-12-12 17:54:37 +01:00