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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 changed
Fixed
ApiResult.getPropertyto include the exception detail in its warninglog by adding the missing
{0}placeholder.Why the change is needed
Logger.log(Level, String, Object)only substitutes the parameter when themessage contains a
{0}placeholder. Without it,e.getMessage()is silentlydropped and the log shows no detail about the
NoSuchMethodException, makingfailures hard to diagnose.
How the change was tested
This is a single-line log-format fix; it compiles cleanly and requires no
behavioral changes to test. Not verified against a running server.
Related issues
Fixes #44
Compatibility / upgrade impact
None — log message text only.