Make chunk sizes configurable for ProcessBuilder
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- scala
- Domain
- operating-systems
Research direction
Locate the JVM implementation of ProcessBuilder.spawn and inspect how stdout and stderr currently read 8192-byte chunks. Check how the existing stdout and stderr APIs are tested, then make the chunk size configurable while preserving the current default of 8192 and verify large transfers use the requested size.
Written by the indexing model from the issue text.
Description
The JVM implementation for the stdout and stderr streams for Processes generated by ProcessBuilder.spawn currently use a chunk size of 8192. While this is probably fine for most use cases I've noticed that it can limit throughput drastically when large amounts of data are transferred this way.
It would be helpful, if the chunk size would be a parameter, either of ProcessBuilder or by having a variant of stderr that takes a chunkSize parameter like
def stdout(chunkSize: Int = 8192): Stream[F, Byte]
- Dominant language
- Scala
- Stars
- 2.5k
- Forks
- 633
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 5
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from typelevel/fs2
-
Reading from a socket gets stuck on Node.js 26Possibly taken A pull request linked to this issue is open or already merged. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 3 days
-
Unix socket bind may delete an existing file when binding failsPossibly taken @abhinav-phi claimed this 3 days ago. Openbug
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Maintainers usually reply within 3 days
-
Scala Native TLSSocket#applicationProtocol behavior is inconsistent with JVMPossibly taken @reardonj claimed this 19 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
Maintainers usually reply within 3 days
-
Feature Proposal: report progress writing to socketsPossibly taken @reardonj claimed this 26 days ago. Open
Difficulty 5/5 Over a week Newbie friendliness 45/100
Maintainers usually reply within 3 days
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
typelevel/fs2#3719 · 2 comments ·
Maintainers usually reply within 3 days
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
propensive/soundness#2351 ·
Maintainers usually reply within 1 day
-
Traffic event delivered/rejected counters appear swapped in TrafficStateController.updateWithReceiptOpen
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
digital-asset/canton#705 ·
Maintainers usually reply within 2 days
-
easy first-contributor first-contributors good first issue help wanted scala up-for-grabs
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
fork-commit-merge/fork-commit-merge#8457 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 78/100
promovolve/promovolve#358 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
svroonland/zio-kinesis#1431 ·