Skip to content

run appears to be stuck (due to buffer limit?) #44

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.

Sign up for GitHub

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

Jump to bottom
Open
itingliu opened this issue May 14, 2025 · 1 comment · May be fixed by #45
Open

run appears to be stuck (due to buffer limit?) #44

itingliu opened this issue May 14, 2025 · 1 comment · May be fixed by #45
Assignees
@iCharlesHu
Labels
blocker Show stopping issues for 0.0.1 bug Something isn't working

Comments

@itingliu
Copy link
Contributor 

let result = try await Subprocess.run(
    .path("/bin/cat"),
    arguments: ["path/to/some/large/text/file.txt]
)

This looks like it is stuck and never returns. It is because the file content exceeds the default limit, and cat is waiting to write more to the output buffer.
@itingliu itingliu added the bug Something isn't working label May 14, 2025
@iCharlesHu
Copy link
Contributor

For this one we decided to just remove the default buffer size limit, but still allow you to set one if you choose to.

@iCharlesHu iCharlesHu self-assigned this May 15, 2025
@iCharlesHu iCharlesHu linked a pull request May 15, 2025 that will close this issue
Open
@iCharlesHu iCharlesHu added the blocker Show stopping issues for 0.0.1 label May 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@iCharlesHu iCharlesHu

Labels
blocker Show stopping issues for 0.0.1 bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Remove the default output buffer limit iCharlesHu/swift-subprocess
2 participants
@iCharlesHu @itingliu