oxalorg / oxalorg/4ever-clojure
Page gets bricked when the invalid code is loaded
Open
Nobody has claimed this yet.
- Dominant language
- Clojure
- Stars
- 271
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
I've bricked the problem page by inputting this invalid code:
(->> (loop [i 0]
(lazy-seq (cons i (recur (inc i)))))
(take 5))
Use it in incognito window because SCI analyzer will crash and the problem page won't load anymore.
Contributor guide
No contributing guide indexed for this repository
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
Reproduce the crash with the supplied code in an incognito window, then trace the SCI analyzer path used by the problem page. Done means this invalid input no longer bricks the page and the problem page remains loadable afterward.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100