-
Notifications
You must be signed in to change notification settings - Fork 130
fix: fix client leaked pipes #2474
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
MasterPtato
wants to merge
1
commit into
05-25-fix_container-runner_fix_leaked_pipes
from
05-26-fix_fix_client_leaked_pipes
Closed
fix: fix client leaked pipes #2474
MasterPtato
wants to merge
1
commit into
05-25-fix_container-runner_fix_leaked_pipes
from
05-26-fix_fix_client_leaked_pipes
Conversation
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
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR Summary
This PR addresses client pipe leaks by updating the nix crate dependency and improving pipe handling across the codebase.
- Updated workspace-level
nixdependency from v0.27 to v0.30 in/Cargo.tomlfor improved Unix system operations - Clarified pipe cleanup behavior in
/packages/edge/infra/client/manager/src/runner.rswith RAII guarantees - Standardized
nixdependency usage across packages by moving configuration to workspace level - Removed explicit feature flags for
nixin/packages/edge/services/pegboard/Cargo.tomlin favor of workspace defaults
4 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile
Deploying rivet with
|
| Latest commit: |
147d554
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://03c8125d.rivet.pages.dev |
| Branch Preview URL: | https://05-26-fix-fix-client-leaked.rivet.pages.dev |
Merge activity
|
graphite-app bot
pushed a commit
that referenced
this pull request
May 26, 2025
<!-- Please make sure there is an issue that this PR is correlated to. --> ## Changes <!-- If there are frontend changes, please include screenshots. -->
This was referenced May 27, 2025
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.

Changes