Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When log lines are appearing in different runs off the log recorder, but have the same timestamp, they would be omitted, as the "last" log line already has this timestamp.
Some details of the analysis, how I came to the tests of that PR:
There is a greyhound night game here: https://greyrcon.de:82/games/2648
The player
🅶 I|I marsmyk
has 41 kills according to the stats page. In-game and reported by HLU, he has 43 kills, hence supposedly 2 kills are "missing".In HLU, the player has the following kills recorded (excuse the german in the copy, it's just the line number):
(the lines with the dash before are the kills that are missing in the CRCon logs from the database)
The CRCon game logs mention 41 kills only: (retrieved from the Game Logs view, hence from the CRCon database, not the live game data):
Looking closer to the kill at
20:41:06
that is missing I looked directly at the logs returned from the game server, as seen by CRCon (this is an excerpt for this specific absolute time):The second object is the
KILL
event that is missing in the CRCon logs database. It has the exact same time as theKILL
event fromGODSEND
againstWeidemilch
, which is in the logs table of CRCon:My assumption therefore is that the kill of
marsmyk
at that time was simply omitted as the CRCon assumed this event was already saved in the database. The logic for skipping events if they have the same timestamp than the already saved one, is the same for years. However, saving log events to the database as often as 5 minutes only, might have resulted in this issue by not being encountered often, if at all. Reducing this to saving logs every 10 seconds made this issue appear more often.Relying on the timestamp only is not good for identifying duplicate logs, as multiple logs can happen at the exact same time, at least as reported by the game server. Hence, use a combination of the event time, as well as the log message.
HLU Logs:
AUTO_Thu_13_Feb_19.26.txt