You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When viewing topic data, if a time greater than 12:30 is selected in the date picker or an hour greater than 12 is passed via the timestamp parameter, the hour is always converted to something between 0 and 12. This prevents searching via timestamp for messages that occur after 12:59 on any given day.
The cause seems to be the format string used to format the timestamp parameter which has been incorrectly specified as YYYY-MM-DDThh:mm:ss.SSS instead of YYYY-MM-DDTHH:mm:ss.SSS causing the hour to always be converted to a number between 0-12 instead of 0-23.
I am happy to create a PR to fix this if it helps
The text was updated successfully, but these errors were encountered:
When filtering topic data by `timestamp` and also when fetching offsets
for consumer groups by `datetime` we seem to be formatting the hour of
the timestamp using `hh`. In moment.js, this causes the hour to always
have a range between [0-12](https://momentjs.com/docs/#/displaying/format/)
even though even though the api expects a range between 0-24. This prevents
filtering of timestamp or fetching of offsets for any time greater than 12:59
on any given day.
This PR corrects this by changing `hh` to `HH` on the formatting calls.
close#550
When viewing topic data, if a time greater than 12:30 is selected in the date picker or an hour greater than 12 is passed via the
timestamp
parameter, the hour is always converted to something between 0 and 12. This prevents searching via timestamp for messages that occur after 12:59 on any given day.The cause seems to be the format string used to format the timestamp parameter which has been incorrectly specified as
YYYY-MM-DDThh:mm:ss.SSS
instead ofYYYY-MM-DDTHH:mm:ss.SSS
causing the hour to always be converted to a number between 0-12 instead of 0-23.I am happy to create a PR to fix this if it helps
The text was updated successfully, but these errors were encountered: