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 selecting a datetime in the data explorer, e.g., to filter data for a certain period of time, values between 12 AM and 1 AM cause a confusing representation.
How to reproduce?
When selecting a datetime within the data explorer
from 12 AM on
the value is then converted to 24:00 which is confusing.
Even worse, when selecting a time after 12 AM
it is displayed as 24:xx which is just wrong.
Expected behavior
Datetime values between 12 AM and 1 AM should be displayed as 00:xy.
Additional technical information
No response
Are you willing to submit a PR?
None
The text was updated successfully, but these errors were encountered:
Hi @bossenti, I found the root cause of the problem. The backend unix timestamp is correct despite showing 24:xx, so the filter by time should still work. I have submitted a one line change PR that should fix the display problem caused by browser (tested on Chrome and Edge).
* implement new round processor
* add English locale, icon, and documentation
* fix checkstyle
* support different rounding modes
* add rounding mode in documentation
* fix time display
Apache StreamPipes version
dev (current development state)
Affected StreamPipes components
UI
What happened?
When selecting a datetime in the data explorer, e.g., to filter data for a certain period of time, values between 12 AM and 1 AM cause a confusing representation.
How to reproduce?
When selecting a datetime within the data explorer
from 12 AM on
the value is then converted to
24:00
which is confusing.Even worse, when selecting a time after 12 AM
it is displayed as
24:xx
which is just wrong.Expected behavior
Datetime values between 12 AM and 1 AM should be displayed as
00:xy
.Additional technical information
No response
Are you willing to submit a PR?
None
The text was updated successfully, but these errors were encountered: