You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 18, 2023. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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\"} }"
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.
The text was updated successfully, but these errors were encountered: