-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Fix duplicate events bug #14020
Fix duplicate events bug #14020
Conversation
The |
What was the cause of the duplicated events? Was it not including a the latest event timestamp in the query?
|
The main cause is that the Silk environment is around 12 minutes ahead of the actual time. Since in my original implementation, I didn't include There was likely duplication also due to the multiple variables I juggled when determining the event timestamp, like having |
The |
* Fix silk events bug * Add ending time for event query * Update debug log level from warn to error * Add freezegun to agent-requirements * Limit freezegun testing to Py3 * Use 0.3.15 instead of new non-Py2 version to support Py2 * Fix style 1981148
What does this PR do?
This PR simplifies the event collection logic since it was causing a bug where the same event was being sent over and over again rather than new events.
Motivation
Bug
Additional Notes
Review checklist (to be filled by reviewers)
changelog/
andintegration/
labels attachedqa/skip-qa
label.