luckyframework / luckyframework/lucky_flow
Figure out way to improve stack trace when fails to connect to Chromedriver
Open
- Dominant language
- Crystal
- Stars
- 55
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
Right now there are lots of loops so the stacktrace is huge. Maybe using a `while` would shorten that up
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the connection and retry loops used when Chromedriver fails to connect. The issue does not name files or tests; done means preserving connection behavior while producing a substantially shorter, more useful stack trace.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- crystal
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100