Skip to content
This repository has been archived by the owner on Dec 18, 2023. It is now read-only.

Provide a clue as to the reason why a gateway request timed out #227

Closed
lanzafame opened this issue Jul 22, 2022 · 1 comment
Closed

Provide a clue as to the reason why a gateway request timed out #227

lanzafame opened this issue Jul 22, 2022 · 1 comment

Comments

@lanzafame
Copy link

Given the nature of the system involved in making requests to the IPFS network, knowing if a request timed out because no peer could be found to have the cid requested versus the node providing it was taking a long time to send the data and we should remake the request, would be super useful.

@lanzafame
Copy link
Author

oooohh nvm, this already happens as in a request timeout is the case where a peer with the content has been found and the data didn't transfer in time. There is a separate error entirely for when a peer with the content couldn't be found, i.e. "status: InvalidArgument, message: \"missing providers for: QmVE2J2sCdiPMZw6vFY92i6FdSreTg3RRvUFcv7Md78vGH\", details: [], metadata: MetadataMap { headers: {\"content-type\": \"application/grpc\", \"date\": \"Fri, 22 Jul 2022 01:41:55 GMT\", \"content-length\": \"0\"} }"

@Arqu Arqu closed this as completed Sep 29, 2022
@dignifiedquire dignifiedquire transferred this issue from n0-computer/iroh Feb 17, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants