Error: Unexpected error
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 142
- Forks
- 230
- PR merge metrics
- No merged PRs in 30d
Description
I encountered the following error on lit.dev:
> Unexpected error
> Error calling GitHub API PATCH /gists/dc2fb1d494889722a580dd315773203e (HTTP status 422)
Stack trace:
```
Error: Error calling GitHub API PATCH /gists/dc2fb1d494889722a580dd315773203e (HTTP status 422)
at y (https://lit.dev/js/components/litdev-playground-page.js:17:396)
at async C.updateGist (https://lit.dev/js/components/litdev-playground-page.js:27:5527)
```
URL: https://lit.dev/playground/#gist=dc2fb1d494889722a580dd315773203e
Site version: `prod-42d1ed5`
Browser: `Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36`
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 at the playground URL and inspect the reported updateGist path in js/components/litdev-playground-page.js, especially the PATCH /gists request. Reproduce the failure with the supplied gist if possible and identify why GitHub returns HTTP 422; done means the playground updates the gist without showing “Unexpected error.”
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, typescript
- Domain
- api, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100