CBOR encoding/decoding issue with timestamps

[janpaul123]

When I subscribe to a topic with the default JSON encoding and subscribe to a basic topic like /connected_clients, then fields of type time are correctly encoded, e.g. { "secs": 1577313146, "nsecs": 190 }.

However, when using the exact same code but using CBOR compression (compression: "cbor") I get this: { "115,101,99,115": 1577313146, "110,115,101,99,115": 190 }. Note that those numbers represent the ASCII values of "secs" and "nsecs".