fix(logger): fix REPORT_CB/2 CRASH logs #9923
Merged
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
zmstone
force-pushed
the
0206-fix-logger-formatter-crash
branch
2 times, most recently
from
797da9d
to
26fa8f6
Compare
zmstone
force-pushed
the
0206-fix-logger-formatter-crash
branch
from
26fa8f6
to
4653ca6
Compare
zhongwencool
approved these changes
Feb 6, 2023
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.
Fixes: #9920
Bug introduced in: #9861
See also EMQX-8882
The text formatter should not change maps to list.
This is usually not an issue, but for logs which has its own
reporter_cbsuch asproc_lib:crash_report/4andgen_server:error_info, the callback matches onmap()type.