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

Bug: Setting timeouts messing with timestamps and causes extra recordings #14

Closed
brenapp opened this issue Nov 20, 2022 · 0 comments
Closed

Bug: Setting timeouts messing with timestamps and causes extra recordings #14

brenapp opened this issue Nov 20, 2022 · 0 comments
Assignees
@brenapp
Labels
bug Something isn't working

Comments

@brenapp
Copy link
Owner

brenapp commented Nov 20, 2022

The current system of tracking which match is running based on remembering the most recent queue has an issue handling timeouts, causing extra recordings and messed up (and out-of-order) timestamps. The system should identify and ignore all timer events associated with timeouts.
@brenapp brenapp added the bug Something isn't working label Nov 20, 2022
@brenapp brenapp self-assigned this Nov 20, 2022
@brenapp brenapp mentioned this issue Jul 19, 2023
Merged
@brenapp brenapp closed this as completed Jul 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@brenapp brenapp

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@brenapp