Skip to content

Conversation

@tina80lvl
Copy link

@tina80lvl tina80lvl commented Sep 21, 2020

@tina80lvl
Copy link
Author

Previous value 1572851662.9782631 corresponded 04.11.2019 10:14:22, not 03.11.2019 23:14:22 as written in comments

Copy link
Collaborator

@mf2199 mf2199 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The epoch timestamp [seconds] for Sunday, 3 November 2019 23:14:22 UTC is 1572822862, not 1572812062, as can be verified here. So either the value or the comment needs to be updated.

@mf2199
Copy link
Collaborator

mf2199 commented Sep 21, 2020

@tina80lvl Could you please also add a meaningful description to this PR. If it refers to an issue, then somewhere in that description should be a reference to it in a form of Fixes: #[issue-number]. The description can later be transfered to the corresponding public PR, so there is no danger of duplicating the effort.

@tina80lvl
Copy link
Author

The epoch timestamp [seconds] for Sunday, 3 November 2019 23:14:22 UTC is 1572822862, not 1572812062, as can be verified here. So either the value or the comment needs to be updated.

I'v found the problem. 1572812062 will be correct time in GMT+03:00, but absolute correct time is 1572822862. Test covers both values with GTM and without but I guess here can be mistake, I'll fix

Copy link
Collaborator

@IlyaFaer IlyaFaer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, as it's seems to be working fine, I think we can create a public PR

@mf2199 mf2199 merged commit 9526cc2 into master Sep 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Couple of tests are permanently broken while running locally

5 participants