Change log level for starting response streaming from info to debug - #2514
Merged
Conversation
sankettangade
approved these changes
Aug 4, 2026
dscpinheiro
approved these changes
Aug 4, 2026
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
3 participants
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.
Description of changes:
Notice while playing with ASP.NET Core Lambda response streaming that we were always adding a info log statement that should only be there if using debug. Made the simple switch.
Amazon.Lambda.AspNetCoreServer.Hosting is in the list of projects to be released but there are no changes. The point is t release taking in the new dependency of Amazon.Lambda.AspNetCoreServer from it's project reference.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.