docs: document DEBUG log level for virtual-thread executor close#129
Merged
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.
Summary
VirtualThreadAsyncHttpClient.close()emits anexecutor.closedevent when it shuts down the backing virtual-thread executor. That event is logged viaClientLogger.atVerbose(), which mapsLogLevel.VERBOSEto SLF4JDEBUG. The chosen level was previously undocumented, leaving readers to wonder whether DEBUG was deliberate or an oversight.This adds one KDoc sentence on
close()recording that theexecutor.closedevent logs at DEBUG by design: closing the executor is a routine lifecycle event, not an operationally noteworthy condition that warrants a higher level.No behavior change — documentation only.
Closes #10