Handle unencodable payloads when publishing to Redis

Merged
PU
9d ago
+84-30

When scaling is enabled, RedisPublishClient::publish does not check the result of json_encode. A payload that cannot be encoded (for example, one that contains INF) is published as an empty string, and the subscriber then fails to decode it.

This change encodes with JSON_THROW_ON_ERROR, so the error stays with the request that caused it. The subscriber also logs a message that it cannot handle and continues with the next one.

Valid payloads are published the same way as before, so no existing behaviour changes.