fix: lwt error and standardize log level length #21
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.
Complex topics that publish
_type: lwt
would cause geogdo to log errors about not being able to parse lat/lng from the json payload. While a graceful error, this caused noise. This commit checks for_type: lwt
and logs a debug message instead of an error.Also standardizing the length of log level status in log line outputs to 3 chars (e.g.
INFO
->INF
,DEBUG
->DBG
, etc).Finally, standardizes line endings to LF.