Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The UTC / Local dropdown does not work #17877

Closed
riccardotommasini opened this issue Apr 28, 2020 · 1 comment · Fixed by #17992, #18011 or #19146
Closed

The UTC / Local dropdown does not work #17877

riccardotommasini opened this issue Apr 28, 2020 · 1 comment · Fixed by #17992, #18011 or #19146

Comments

@riccardotommasini
Copy link

riccardotommasini commented Apr 28, 2020

Steps to reproduce:

List the minimal actions needed to reproduce the behavior.

  1. add an event at 2020-01-01 12:00:00 UTC
test,sometag=t somefield=1 1577880000 
  1. search for it in flux
from(bucket: "test")
  |> range(start: 2020-01-01T11:50:00Z, stop: 2020-01-01T12:10:00Z)

Actual behavior:
I find it

Screenshot 2020-04-27 at 15 17 11

  1. in the UI,  select UTC in the dropdown and use the calendar field to run the same query
    Screenshot 2020-04-27 at 15 20 59

expected behavior:
I find it as before

Actual behavior:
Not getting any result

Image 27-04-2020 at 15 22

  1. do the same assuming that the data point has a local time. Look for it between 13:00 and 14:00 (but the selector is on UTC)

Actual behavior:
Image 27-04-2020 at 15 25

NOTE: I obtain the same result even if I switch to local
Screenshot 2020-04-27 at 15 25 53

CONCLUSION: the UTC / Local dropdown does not work

Environment info:

@asalem1
Copy link
Contributor

asalem1 commented Jul 29, 2020

I'm gonna reopen this since it doesn't seem to be working:

  1. For users who's current timezone is GMT (or anywhere East of GMT - i.e. +1 UTC)
  2. On the dashboard page

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment