-
Notifications
You must be signed in to change notification settings - Fork 38
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
Lines in first write of combat log file are ignored #455
Comments
Reproduced by dropping this bit from the test scripts:
|
A user reported this, here's some logs (see the final DHT): WarcraftRecorder-2023-11-19 (3).log The top of the combat log file:
|
This is merged to main now under 4a7f6a8. I've done some testing and seems OK so far. We've lost the locking of a combat log, but I think that's fine. Bit nervous about multi-box confusion but I'm going to state that's not supported. |
Theory is this:
Surely the fix is to read any existing content in a newly spotted combat log file before we start tailing.
The text was updated successfully, but these errors were encountered: