The timestamp metadata returned to clients shows incorrect timezone offsets when reverting back to UTC (as writting normalized UTC code in server and client side).
Using the long timestamp in the JetStreamTestBase1605139610113260000 corresponding to a
2020-11-12T00:06:50.113260Z RFC3339 it results to a ZonedDateTime of (ie)
2020-11-12T00:06:50.113260+01:00[Europe/Madrid] returned in the timestamp metadata.
Observed behavior
The timestamp metadata returned to clients shows incorrect timezone offsets when reverting back to UTC (as writting normalized UTC code in server and client side).
Using the long timestamp in the JetStreamTestBase 1605139610113260000 corresponding to a 2020-11-12T00:06:50.113260Z RFC3339 it results to a ZonedDateTime of (ie) 2020-11-12T00:06:50.113260+01:00[Europe/Madrid] returned in the timestamp metadata.
Converting it back to UTC:
Gives back a 2020-11-11T23:06:50.113260Z[UTC] which is wrong.
Expected behavior
The above conversion to UTC should be 2020-11-12T00:06:50.113260Z[UTC]
Server and client version
server: Synadia current Cloud NGS service (@connect.ngs.global) client: io.nats:jnats-2.16/17.x
Steps to reproduce
Given a NATS Message's metadata timestamp:
The converted back to UTC ZonedDateTime timestamp utcZonedDateTime is wrong.