This repository has been archived by the owner on Mar 25, 2022. It is now read-only.
Deploy latest go-ipfs master to the Gateways and bootstrappers #415
Labels
P0
Critical: Tackled by core team ASAP
Comments
|
We should just cut a release (and I have to eat my own words about performance regression tests not being extremely important, this kind of bug doesn't show up on localhost -> localhost; go -> go transfers). |
Okay on it |
ghost
closed this as This issue was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
0.4.16 introduced a regression that makes transfers of
go => JSalmost certainly fail (more context here ipfs/interop#28). @Stebalien already fixed it but it hasn't been released.Can we have the gateways with latest go-ipfs master so that things go as smooth as possible for the demos coming?
An alternative solution is to get another go-ipfs release next week and updating the gateways with that. Just putting the two options there, the second is better but we need at least one of them.
The text was updated successfully, but these errors were encountered: