Skip to content

Remove the default output buffer limit #45

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

iCharlesHu
Copy link
Contributor

This PR removes the output buffer limit by default when setting .string or .bytes as output or error.

Resolves #44

@iCharlesHu iCharlesHu requested review from parkera and itingliu May 15, 2025 04:24
@iCharlesHu iCharlesHu marked this pull request as ready for review May 15, 2025 04:24
@@ -240,10 +240,9 @@ extension OutputProtocol where Self == FileDescriptorOutput {
@available(SubprocessSpan, *)
#endif
extension OutputProtocol where Self == StringOutput<UTF8> {
/// Create a `Subprocess` output that collects output as
/// UTF8 String with 128kb limit.
/// Create a `Subprocess` output that collects output as UTF8 String
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the documentation comment here should say that the buffer is unlimited, so the amount of memory required is proportional to the size of the output.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good

@iCharlesHu
Copy link
Contributor Author

Updated header doc to indicate that .string and .bytes have unlimited buffer size.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

run appears to be stuck (due to buffer limit?)
2 participants