Fix missing stream error handling in web video object storage proxy#7535
Merged
Chocobozzz merged 1 commit intoApr 13, 2026
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
This PR aligns the object-storage web video proxy behavior with the existing HLS proxy by ensuring stream errors are properly captured and handled, preventing unhandled stream error events from crashing the Node.js process.
Changes:
- Replaced
stream.pipe(res)withpipeline(stream, res, cb)inproxifyWebVideoFile. - Routed mid-stream failures to the existing
handleObjectStorageFailurehandler (matching the HLS proxy pattern).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Owner
|
Thanks! |
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
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
Was debugging intermittent crashes on a self-hosted instance using S3-compatible storage and traced the issue to
proxifyWebVideoFileinserver/core/lib/object-storage/proxy.ts.The web video proxy uses
stream.pipe(res)(line 30) without any stream error handler. If the S3 stream errors mid-transfer (connection drop, object deleted during download, S3 timeout), the error event goes unhandled, which can crash the Node.js process.The HLS proxy in the same file already handles this correctly using
pipeline()with an error callback (lines 60-69). The web video proxy should do the same.Before: If the S3 connection drops during a web video download, the stream emits an unhandled error event. Depending on the Node.js configuration, this either crashes the process or silently corrupts the response.
After: Stream errors during web video proxying are caught and handled by
handleObjectStorageFailure, which logs the error and returns an appropriate HTTP error response — the same behavior that already exists for HLS streaming.Every other
.pipe()call in the server codebase (plugin-manager.ts:571,user-exporter.ts:122) has an explicit error handler. This brings the web video proxy in line with the rest.Related issues
N/A — found by reading the code
Has this been tested?
stream.pipe(res)withpipeline(stream, res, errorCallback)) and follows the exact pattern fromproxifyHLSin the same fileScreenshots
N/A