luckyframework / luckyframework/lucky_cli
Broken specs on macOS
Open
Nobody has claimed this yet.
help wanted
- Dominant language
- HTML
- Stars
- 92
- Forks
- 48
- PR merge metrics
- No merged PRs in 30d
Description
When I run specs locally on my machine, they ALWAYS fail. I usually get about 6 failures saying expected status code of 0 got 256. This wasn't always the case though. I feel like it started with Big Sur. Could it be iTerm? or Big Sur specific? Something to look in to.
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 by reproducing the specs locally on macOS, recording the six failures and the commands that return status code 256. Compare the affected environment with the reported Big Sur and iTerm setups; done means the specs pass on the affected macOS configuration or the cause is clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- crystal
- Domain
- cli, operating-systems, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100