Fix ShellBolt log level#7955
Merged
Merged
Conversation
Contributor
Author
|
Fixes #7954 |
rzo1
approved these changes
Feb 4, 2025
rzo1
left a comment
Contributor
There was a problem hiding this comment.
Thanks for the PR - very much appreciated! This is a regression from the switch to another json impl in the last year.
Contributor
Author
A colleague told me that it was introduced with 2.6.0, but I haven't found the exact commit. |
Contributor
|
@mstrucken Most likely: STORM-3961 :) |
reiabreu
approved these changes
Feb 4, 2025
reiabreu
approved these changes
Feb 4, 2025
Contributor
|
Thanks for a detailed issue and PR! |
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
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.
What is the purpose of the change
ShellBolt log level is always INFO due to failed check against Long after deseralizing
How was the change tested
I used the following minimal example: