[Transit Departures (Catenary for Raycast)]...
Open
Nobody has claimed this yet.
bug
extension
extension: catenary-raycast
- Dominant language
- TypeScript
- Stars
- 7.8k
- Forks
- 6.9k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 442
Description
Extension
https://raycast.com/quacksire/catenary-raycast
Raycast Version
v1.104.15
OS Version
No response
Description
Error:
SyntaxError: Unexpected end of JSON input
at JSON.parse (<anonymous>)
at parseJSONFromBytes (node:internal/deps/undici/undici:5880:19)
at successSteps (node:internal/deps/undici/undici:5861:27)
at fullyReadBody (node:internal/deps/undici/undici:4753:9)
at process.processTicksAndRejections (node:internal/process/task_queues:103:5)
at async consumeBody (node:internal/deps/undici/undici:5870:7)
at async /Users/danielgonzalez/.config/raycast-x/extensions/197047a7-737c-4aa3-850d-28356fa867d6/check-departures.js:8:4817
Steps To Reproduce
- Open the command to find nearby departures
- The command errors out
Current Behaviour
No response
Expected Behaviour
No response
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 opening the Catenary Raycast extension from the linked extension page and reproducing the nearby-departures command. Inspect check-departures.js at the stack-trace location and determine why the command receives input that cannot be parsed as JSON; done means the command returns nearby departures without the reported error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100