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

Mexico City Timezone Data Incorrect, time off by one hour #2889

Closed
2 of 5 tasks
indierodo opened this issue May 9, 2024 · 2 comments
Closed
2 of 5 tasks

Mexico City Timezone Data Incorrect, time off by one hour #2889

indierodo opened this issue May 9, 2024 · 2 comments

Comments

@indierodo
Copy link

Search before asking

  • I had searched in the issues and found no similar issues.

Operating System

  • macOS
  • Windows
  • Linux

Operating System Version

macOS 14.2

It happens on the web browser too?

No, it just happens on the Desktop app

Rocket.Chat Desktop App Version

3.9.14

Rocket.Chat Server Version

6.5

Describe the bug

Similar bug as #1181 and #1391 , when I run the Electron App with the Mexico City Timezone configured in System Settings in macOS 14.2 (see attached image), I find that the time is off by one hour. Changing the Timezone in System Settings to another city with same timezone (Tegucigalpa, Honduras) corrects the problem, it is an specific problem with Mexico City timezone: America/Mexico_City

image

How to Reproduce

  1. Configure Timezone in MacOS Settings to Mexico City.
  2. On Rocket.Chat, click on any chat and check the time of the messages, they should be off by one hour.

Describe your Expected behavior

The time should be the same, however it is off by one hour.

image image

Anything else

Mexico removed its daylight savings time not long ago. Same as with #1391 #1181, this problem might be related to Electron and Node.js rather than Rocket.Chat.

Thanks for your attention.

Are you willing to submit a code contribution?

  • Yes, I am willing to submit a Pull Request!
@jeanfbrito
Copy link
Collaborator

Can you test our v4.0.0 version? It updated the Electron that may fix your issue. I will close the issue but if not fixed we open it again, ok?

@indierodo
Copy link
Author

@jeanfbrito I can confirm v4.0.0 no longer presents this issue. Thank you for the follow-up.

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

No branches or pull requests

2 participants