Make mpv IPC pipe communication robust with timeouts and retry logic #3
+1,387
−936
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.
The pipe/socket communication with mpv's IPC could block indefinitely, had no retry logic for transient failures, and lacked proper error handling. This made progress reporting unreliable when mpv was slow to start or when temporary system issues occurred.
Changes
Retry with exponential backoff
checked_powto prevent overflowTimeouts and bounds
Connection validation
Error handling
Error::from_win32()withError::from(std::io::Error)for forward compatibility with future windows crate versionsResource cleanup
Example
Windows Crate Compatibility Note: The code now uses Error APIs compatible with both windows 0.59 (current) and future versions. Windows 0.62.x has a known bug with windows-future 0.3.2 incompatibility; will upgrade to 0.63+ when available on crates.io.
Changes are backward compatible with no new dependencies.
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.