Insteon: Add Milliseconds Detail to Debug Level 4 Messages #179
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Messages arrive very very fast. Adding milliseconds to the print log helps debug what is going on.
Trailing zeros were previously omitted. Printing the milliseconds helps a lot in debugging corrupt messages
krkeegan
added a commit
that referenced
this pull request
May 21, 2013
Insteon: Add Milliseconds Detail to Debug Level 4 Messages
|
ARG! I messed this one up. hollie can you revert this merge? I think it is just: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This changes the log entries which look like this:
08/04/2013 18:49:00 [Insteon_PLM] DEBUG4:
To this:
08/04/2013 18:49:00 [Insteon_PLM] DEBUG4: Milliseconds 350.83
This has made it easier to diagnose certain duplicate and corrupt message issues.