Properly parse new log format with dedicated exception field #530
Conversation
This file contains hidden or 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
juliusknorr
force-pushed
the
enh/new-exception-field
branch
from
0fcc6ed to
fcba0d6
Compare
skjnldsv
approved these changes
Jun 15, 2021
Member
Author
|
Anyone can check if you can properly build a bundle that matches the CI check ? It always produces the committed one for me with the same node/npm version |
Merged
juliusknorr
force-pushed
the
enh/new-exception-field
branch
from
fcba0d6 to
898b5cf
Compare
Member
|
/compile amend / |
Signed-off-by: Julius Härtl <[email protected]> Signed-off-by: npmbuildbot-nextcloud[bot] <npmbuildbot-nextcloud[bot]@users.noreply.github.com>
npmbuildbot-nextcloud
bot
force-pushed
the
enh/new-exception-field
branch
from
898b5cf to
770c016
Compare
45 tasks
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.
Companion PR for nextcloud/server#27451 to properly handle the separate exception field in the log object but keeping the old format supported to still properly display existing messages.