提交 447601e5 作者: Steven Allen

CHANGELOG: backport release notes fixes from the blog post

上级 e969e139
...@@ -4,42 +4,41 @@ ...@@ -4,42 +4,41 @@
We're releasing a PATCH release of go-ipfs based on 0.4.21 containing some critical fixes. We're releasing a PATCH release of go-ipfs based on 0.4.21 containing some critical fixes.
The past several releases have been shaky and the network has scaled to the The IPFS network has scaled to the point where small changes can have a
point where where small changes can have a wide-reaching impact on the entire wide-reaching impact on the entire network. To keep this situation from
network. To keep this situation from escalating, we've put a hold on releasing escalating, we've put a hold on releasing new features until we can improve our
new features until we can improve our [release [release process](https://github.com/ipfs/go-ipfs/blob/master/docs/releases.md)
process](https://github.com/ipfs/go-ipfs/pull/6482) (which we will be trialing (which we've trialed in this release) and [testing
in this release) and [testing
procedures](https://github.com/ipfs/go-ipfs/issues/6483). procedures](https://github.com/ipfs/go-ipfs/issues/6483).
This release includes fixes for the following regressions: This release includes fixes for the following regressions:
1. A major bitswap throughput regression introduced in 0.4.21 1. A major bitswap throughput regression introduced in 0.4.21
([ipfs/go-ipfs#6442](https://github.com/ipfs/go-ipfs/issues/6442)). ([ipfs/go-ipfs#6442](https://github.com/ipfs/go-ipfs/issues/6442)).
2. High bitswap CPU usage when connected to many (e.g., 10,000) peers. See 2. High bitswap CPU usage when connected to many (e.g. 10,000) peers. See
[ipfs/go-bitswap#154](https://github.com/ipfs/go-bitswap/issues/154). [ipfs/go-bitswap#154](https://github.com/ipfs/go-bitswap/issues/154).
2. The local network discovery service sometimes initializing before the 2. The local network discovery service sometimes initializes before the
networking module, causing it to announce the wrong addresses and sometimes networking module, causing it to announce the wrong addresses and sometimes
complain about not being able to determine the IP address) complain about not being able to determine the IP address
([ipfs/go-ipfs#6415](https://github.com/ipfs/go-ipfs/pull/6415)). ([ipfs/go-ipfs#6415](https://github.com/ipfs/go-ipfs/pull/6415)).
It also includes fixes for: It also includes fixes for:
1. Pins not being persisted after `ipfs block add --pin` 1. Pins not being persisted after `ipfs block add --pin`
([ipfs/go-ipfs#6441](https://github.com/ipfs/go-ipfs/pull/6441)). ([ipfs/go-ipfs#6441](https://github.com/ipfs/go-ipfs/pull/6441)).
2. Concurrent map access on GC due to the pinner 2. Panic due to concurrent map access when adding and listing pins at the same
([ipfs/go-ipfs#6419](https://github.com/ipfs/go-ipfs/pull/6419)). time ([ipfs/go-ipfs#6419](https://github.com/ipfs/go-ipfs/pull/6419)).
3. Potential pin-set corruption given a concurrent `ipfs repo gc` and `ipfs pin 3. Potential pin-set corruption given a concurrent `ipfs repo gc` and `ipfs pin
rm` ([ipfs/go-ipfs#6444](https://github.com/ipfs/go-ipfs/pull/6444)). rm` ([ipfs/go-ipfs#6444](https://github.com/ipfs/go-ipfs/pull/6444)).
4. Build failure due to a deleted git tag in one of our dependencies 4. Build failure due to a deleted git tag in one of our dependencies
([ipfs/go-ds-badger#64](https://github.com/ipfs/go-ds-badger/pull/65)). ([ipfs/go-ds-badger#64](https://github.com/ipfs/go-ds-badger/pull/65)).
Thanks to: Thanks to:
* @hannahhoward for fixing both bitswap issues. * [@hannahhoward](https://github.com/hannahhoward) for fixing both bitswap issues.
* @sanderpick for catching and fixing the local discovery bug. * [@sanderpick](https://github.com/sanderpick) for catching and fixing the local
* @campoy for fixing the build issue. discovery bug.
* [@campoy](https://github.com/campoy) for fixing the build issue.
## 0.4.21 2019-05-30 ## 0.4.21 2019-05-30
......
Markdown 格式
0%
您添加了 0 到此讨论。请谨慎行事。
请先完成此评论的编辑!
注册 或者 后发表评论