NatLabRockies / NatLabRockies/windwatts
patch console errors: API 500 error and uncaught error
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 10
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 6
Description
It seems backend API is not functioning well - uncaught error + Internal 500 error
index-BPt14E0N.js:132 POST https://windwatts.nlr.gov/api/v1/era5-quantiles/production 500 (Internal Server Error)
Uncaught (in promise) Error: A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received
/?lat=43.4103&lng=-113.3207&zoom=6:1 Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.
/?lat=43.4103&lng=-113.3207&zoom=6:1 Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.
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 request to https://windwatts.nlr.gov/api/v1/era5-quantiles/production from the page URL shown and inspect the reported index-BPt14E0N.js:132 failure. Determine which errors are from the API and which are browser runtime messages. Done means the API request no longer returns 500 and the relevant uncaught error is resolved or clearly explained.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100