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
The current way HTTP requests are handled by the IPFS gateway(ipfs.io right now), timeouts never happen. IIRC, it has something to do how the HTTP request is handled(malformed), but I don't have a reference right now.
Either way, it's causing a big issue with sb install commands that can infinitely hang. Will probably need to run the ipfs fetch as a subcommand, an entirely separate process. That way, we can snag the PID, run our own timeout counter, then kill it if necessary. Threading won't work, and no other methods I've tried in the past will work.
Perhaps worth checking into other gateways.
The text was updated successfully, but these errors were encountered:
The current way HTTP requests are handled by the IPFS gateway(ipfs.io right now), timeouts never happen. IIRC, it has something to do how the HTTP request is handled(malformed), but I don't have a reference right now.
Either way, it's causing a big issue with
sb install
commands that can infinitely hang. Will probably need to run the ipfs fetch as a subcommand, an entirely separate process. That way, we can snag the PID, run our own timeout counter, then kill it if necessary. Threading won't work, and no other methods I've tried in the past will work.Perhaps worth checking into other gateways.
The text was updated successfully, but these errors were encountered: