UnitID alpha improvements and decode error display #785
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 commit will display UnitID alpha in console messages to improve the view of trunk-recorder operations at the
info
logging level and aid in any UID regex debugging. UnitID alpha was previously displayed in trunk-recorder 3.x console logs, and this commit would restore some of that functionality.When a call ends, Call_Concluder will now display known UnitID alpha and any reported errors/spikes for that transmission. Call times are formatted to two decimal places to avoid the initial
pos: 0
creating text alignment issues.If
hideEncrypted
is false (default), UnitID and alpha will also be displayed to provide some insight into the nature of those transmissions.Per discussion re: #764 with @EricTendian, the
format_all
flag is included to allow complex regex matches and conditional substitutions with theunitTagsFile
in addition to the current behavior.