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.
Author Description
(optional)
Deepinfra streams back ping chunks on long requests. They're a weird format, here's what they look like before any processing:
: ping - 2025-04-13 03:55:09.637341+00:00
.Title: Handle ping chunks from deep infra
🔄 What Changed
: ping - 2025-04-13 03:55:09.637341+00:00
are now properly handled🔍 Impact of the Change
📁 Total Files Changed
🧪 Test Added
N/A - No tests were added in this PR
🔒 Security Vulnerabilities
N/A - No security vulnerabilities were addressed
Motivation:
Fixes a bug where DeepInfra ping messages were being incorrectly processed as part of the response data.
Related Issues:
Quality Recommendations
Consider adding unit tests to verify the ping message filtering functionality
Add error handling in case the regex matching fails unexpectedly
Consider adding a comment explaining why these ping messages need to be filtered out