Raku / Raku/whateverable

Proc::Async and large stdin

Open
#216 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

whateverable
Dominant language
Raku
Stars
19
Forks
16
PR merge metrics
No merged PRs in 30d

Description

This is not an active issue in whateverable, but I decided to create this ticket to make sure it does not slip through the cracks.

See 8159c2da613003f4f3b8d030863dc38c45951d00.

If I recall correctly, if you do $proc.print: $foo where $foo is large (hundreds of megabytes), horrible things happen. I think it is an issue in rakudo, but it has to be investigated more so that we get a useful ticket out of it.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing whateverable issue #199 and commit 8159c2da613003f4f3b8d030863dc38c45951d00. Investigate how Proc::Async handles very large stdin writes, reproduce the reported behavior with hundreds of megabytes, and document the findings in a useful Rakudo issue or update this ticket with a clear next step.

Written by the indexing model from the issue text.

Assessment

Domain
operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.