swiftlang / swiftlang/swift-crashlog-processing
Turn off line buffering if needed
Open
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 3
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Originally posted by @al45tair in https://github.com/swiftlang/swift-crashlog-processing/pull/1#discussion_r3497821735
Assess if this is needed and find platform appropriate approaches...
From CrashScanner.swift...
// get the input file descriptor
// if isatty(), turn off line buffering with
// get input FILE *
// call setvbuf(stream, nil, _IONBF, 0)
Contributor 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.
Research direction
Start in CrashScanner.swift at the input file-descriptor handling and inspect how isatty() and input buffering are currently used. Assess whether line buffering must be disabled, identify a platform-appropriate approach, and verify that the resulting behavior is correct for the relevant input stream.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100