Ensure Newline After HTTP Body in debug_dev Output #478
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.
🧩 Ensure Newline After HTTP Body in debug_dev Output
📌 Problem
When using HTTPClient#debug_dev with a shared output (e.g., writing to $stdout), the HTTP response body is written without a trailing newline. This leads to problems when the stream is reused for other log outputs
In some systems, this prevents proper JSON log parsing, causing logs to be dropped entirely.
✅ Solution
This PR ensures that a newline is always written after the HTTP response body when using debug_dev. This makes debug_dev safer to use with shared output streams like $stdout or a Tee stream, where multiple JSON logs may be written in sequence.
🔬 Tests
Two new tests are added to verify this behavior:
• test_debug_dev_shared_dev
• test_debug_dev_stream_shared_dev
These assert that any content appended to the shared debug_dev stream after a request appears on a new line, preventing log merging.
@nahi