Closed daviddias closed 6 years ago
//cc @lgierth @Stebalien @whyrusleeping
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).
Can we have the gateways with latest go-ipfs master so that things go as smooth as possible for the demos coming?
Okay on it
0.4.16 introduced a regression that makes transfers of
go => JS
almost certainly fail (more context here https://github.com/ipfs/interop/pull/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.