Crash report: `RelayNetwork: No data returned for operation `CollectionQuery`, got error(s):Rate limit exceededSee the error `source` property for more information.`
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.5k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
URL
https://app.uniswap.org/#/nfts/collection/0xbce3781ae7ca1a5e050bd9c4c77369867ebc307e
Error
RelayNetwork: No data returned for operation `CollectionQuery`, got error(s):
Rate limit exceeded
See the error `source` property for more information.
Stacktrace
RelayNetwork: No data returned for operation `CollectionQuery`, got error(s):
Rate limit exceeded
See the error `source` property for more information.
at r (https://app.uniswap.org/static/js/4.ef60cbe2.chunk.js:2:2961587)
at Object.create (https://app.uniswap.org/static/js/4.ef60cbe2.chunk.js:2:2961859)
at https://app.uniswap.org/static/js/4.ef60cbe2.chunk.js:2:3677257
at Array.forEach (<anonymous>)
at t._handleErrorResponse (https://app.uniswap.org/static/js/4.ef60cbe2.chunk.js:2:3677018)
at t._handleNext (https://app.uniswap.org/static/js/4.ef60cbe2.chunk.js:2:3678089)
at https://app.uniswap.org/static/js/4.ef60cbe2.chunk.js:2:3676810
at e.exports (https://app.uniswap.org/static/js/4.ef60cbe2.chunk.js:2:3692934)
at https://app.uniswap.org/static/js/4.ef60cbe2.chunk.js:2:3676794
at t._schedule (https://app.uniswap.org/static/js/4.ef60cbe2.chunk.js:2:3676334)
Device data
{
"ua": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/107.0.0.0 Safari/537.36",
"browser": {
"name": "Chrome",
"version": "107.0.0.0",
"major": "107"
},
"engine": {
"name": "Blink",
"version": "107.0.0.0"
},
"os": {
"name": "Mac OS",
"version": "10.15.7"
},
"device": {},
"cpu": {}
}
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 failure at the reported NFT collection URL and inspect the CollectionQuery request behind the RelayNetwork error. Use the provided stack trace to investigate how the rate-limit response is handled; done means the collection no longer crashes when that error occurs or presents a confirmed, usable error state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100