-
Notifications
You must be signed in to change notification settings - Fork 705
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
Timestamp is off by -1 hour #1181
Comments
May I ask you in which timezone you are? |
Central Daylight Time. GMT-5.
…On Wed, Apr 17, 2019, 11:33 PM Tasso Evangelista ***@***.***> wrote:
May I ask you in which timezone you are?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1181 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAGRMZB4S7PX3U7M775RFNLPQ722DANCNFSM4HGBVP6A>
.
|
We are having the same issue with the macOS App V 2.16.0 but in the web app the hour is correct at least in Chrome. It shows +1 hour and our timezone is GMT-3. |
@paulopera The origin of this bug lies on Node: nodejs/node#30211 |
@tassoevan Thanks for reaching out and hope they could fix the problem. |
Please test if the latest release did solve this. If not please reopen the issue or create a new one and tell us. I will be closing this one for now. Thank you! |
My Setup
Description
When viewing Rocket.Chat in the Electron Desktop app, all timestamps are off by -1 hour. e.g. If it's 11:32 AM, I see everything as 10:32 AM. If I load the server in the browser, on the same computer, I correctly see it as 11:32.
Current Behavior
Timestamps are off by -1 hour
Expected Behavior
Timestamps use current computer time.
I have uninstalled/reinstalled. I checked remove user data and even manually removed
AppData/Roaming
before installing. The issue started around the time Daylight Savings time went into effect. I've also traveled to another timezone and the timestamps worked then, but reverted back to -1 once I returned to my normal timezone. No other users on this server have reported this issue.The text was updated successfully, but these errors were encountered: