We do not handle error response from the estuary.
- Dominant language
- TypeScript
- Stars
- 11
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
https://github.com/kodadot/nft-gallery/issues/2151
In this call:
https://github.com/kodadot/workers/blob/5a16d0a7add260110b79c584e02d220f9291525f/pinning/src/lib.rs#L101
I expect
https://github.com/kodadot/workers/blob/5a16d0a7add260110b79c584e02d220f9291525f/pinning/src/lib.rs#L19-L23
However as reported by @yangwao:
`error decoding body response`
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with pinning/src/lib.rs at line 101 and compare the response handling with lines 19-23. Reproduce the Estuary error response and trace the body decoding failure; done means the call handles that error response without reporting only “error decoding body response.”
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100