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.

Sign up for GitHub

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

Jump to bottom

timestamp is late for around 5 min. #22

Closed
jaswinder-saini opened this issue Aug 19, 2018 · 2 comments
Closed

timestamp is late for around 5 min. #22

jaswinder-saini opened this issue Aug 19, 2018 · 2 comments

Comments

@jaswinder-saini
Copy link

I noticed that the timestamp is late for around 5 min. how we can check whether canary tokens were fired on time?
@thinkst
Copy link
Collaborator

thinkst commented Sep 21, 2018

Hey @jaswinder-saini,

The timestamp shouldn't be late since it is taken when the request hits the canarytokens server. Ill take a look into this, but in the meantime, would you mind checking that your system clock is correct and tell me which token you triggered that was late?

@thinkst
Copy link
Collaborator

thinkst commented Jan 23, 2019

Closing issue due to inactivity. Please reopen if you have the same issue or want to continue this discussion.

@thinkst thinkst closed this as completed Jan 23, 2019
wleightond pushed a commit that referenced this issue May 5, 2023
@emmanuel-thinkst
T4314 integration test windows folder (#22)
ccb50ab 
* add test windows folder integration test case
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jaswinder-saini