FetchError: request to https://api.uniswap.org/v1/graphql
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.5k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
[graphql] Error: FetchError: request to https://api.uniswap.org/v1/graphql failed, reason: connect ETIMEDOUT 185.60.216.169:443
[graphql] at ClientRequest. (/root/GitCode/interface/node_modules/node-fetch/lib/index.js:1491:11)
[graphql] at ClientRequest.emit (node:events:513:28)
[graphql] at TLSSocket.socketErrorListener (node:_http_client:496:9)
[graphql] at TLSSocket.emit (node:events:513:28)
[graphql] at emitErrorNT (node:internal/streams/destroy:151:8)
[graphql] at emitErrorCloseNT (node:internal/streams/destroy:116:3)
[graphql] at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
[graphql] type: 'system',
[graphql] errno: 'ETIMEDOUT',
[graphql] code: 'ETIMEDOUT'
[graphql] }
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 with the reported request to https://api.uniswap.org/v1/graphql and the node-fetch stack location node_modules/node-fetch/lib/index.js:1491. Reproduce the ETIMEDOUT failure and trace how the GraphQL request is initiated; done requires identifying a project-level cause and a clearly testable resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, node.js, typescript
- Domain
- api, blockchain
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100