-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Event triggers created_at time shifted +09:00 #10308
Comments
Hey @tatsuhirokasai, thanks for raising this issue.
Regarding your suggestion, checkout this comment |
Hey @Varun-Choudhary , Thank you for checking. Here are the answers to your questions:
The actual event occurred at 2:22:32 PM +9:00, but as illustrated in the figure, it was displayed on the console as 23:22:32 +9:00, which is effectively 11:22 PM +9:00.
For the GraphiQL Engine, I have set the following environment variable: For the Postgres server, when I execute the show timezone command, it displays I have not specified a time zone for the browser, but the time zone on my Mac is set to
No, the Postgres server was newly set up. |
Thank you @tatsuhirokasai for the detailed info. We can reproduce this issue. We are actively working to fix it asap. |
Version Information
Server Version: v2.40.0
Environment
OSS
What is the current behaviour?
The created_at values displayed on the Processed Events page and Invocation Logs page in the Hasura Console are offset by 9 hours.
What is the expected behaviour?
The values should display the actual time when the events were executed (i.e., the values should reflect the time 9 hours earlier).
How to reproduce the issue?
Screenshots or Screencast
Please provide any traces or logs that could help here.
Event payload:
Any possible solutions/workarounds you're aware of?
Execute the following SQL commands:
Ref.
#5722
Keywords
event trigger, time zone, TIMESTAMPTZ
The text was updated successfully, but these errors were encountered: