-
Notifications
You must be signed in to change notification settings - Fork 0
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
Cleanup DTLog, implement log levels #39
Conversation
MathNerd28
commented
Oct 12, 2023
- Add version suffix in DTLibInfo
- Remove duplicate mode logging
- Use tryFlush() instead of flush()
- Add constant LOG_PATH_SEPARATOR
- Use RobotController.getTeamNumber() instead of custom implementation
- Change unknown team number to 0
- General cleanup, suppress useless warnings
Implement log levels for variables. They filter variables based on their immediate parent's log level, allowing components to be selectively logged based on the current level. Levels for variables are not denoted in the log output. Also, properly implement log levels for messages. These are denoted in the log, under identifiers 0x0008 through 0x000B. |
Properly log exceptions where applicable (not during startup, DEBUG level when explicitly caught, etc.) |
This PR is ready for review |
writeInt(checksum); | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You might consider something like CRC32 for the checksum: https://docs.oracle.com/javase/8/docs/api/java/util/zip/CRC32.html