Updated known issues for 1.4.6 (#996)

* Updated known issues

Signed-off-by: Madeline <madeline.murray@consensys.net>
pull/998/head
MadelineMurray 5 years ago committed by GitHub
parent 2e8831a07a
commit 3fa0bbfc05
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
  1. 14
      CHANGELOG.md
  2. 22
      KNOWN_ISSUES.md

@ -31,7 +31,19 @@ The [1.5 release](docs/1_5_Upgrade.md) is scheduled for early July.
### Bug Fixes ### Bug Fixes
- Fixed case where networks using onchain permissioning could stall when the bootnodes were not validators. [\#969](https://github.com/hyperledger/besu/pull/969) - Added timeout to queries. [\#986](https://github.com/hyperledger/besu/pull/986)
- Fixed issue where networks using onchain permissioning could stall when the bootnodes were not validators. [\#969](https://github.com/hyperledger/besu/pull/969)
### Known Issues
Known issues are open issues categorized as [Very High or High impact](https://wiki.hyperledger.org/display/BESU/Defect+Prioritisation+Policy).
#### Previously identified known issues
- [Scope of logs query causing Besu to hang](KNOWN_ISSUES.md#scope-of-logs-query-causing-besu-to-hang)
- [Eth/65 loses peers](KNOWN_ISSUES.md#eth65-loses-peers)
- [Fast sync when running Besu on cloud providers](KNOWN_ISSUES.md#fast-sync-when-running-besu-on-cloud-providers)
- [Privacy users with private transactions created using v1.3.4 or earlier](KNOWN_ISSUES.md#privacy-users-with-private-transactions-created-using-v134-or-earlier)
## 1.4.5 ## 1.4.5

@ -5,15 +5,19 @@ in the current release are provided in the [Changelog](CHANGELOG.md).
Known issues are open issues categorized as [Very High or High impact](https://wiki.hyperledger.org/display/BESU/Defect+Prioritisation+Policy). Known issues are open issues categorized as [Very High or High impact](https://wiki.hyperledger.org/display/BESU/Defect+Prioritisation+Policy).
## Eth/65 not backwards compatible ## Scope of logs query causing Besu to hang
[`eth_getLogs` queries that are too large or too broad can cause Besu to never return](https://github.com/hyperledger/besu/issues/944).
Workaround - Limit the number of blocks queried by each `eth_getLogs` call.
A fix for this issue is being actively worked on.
## Eth/65 loses peers
From v1.4.4, `eth/65` is [disabled by default](https://github.com/hyperledger/besu/pull/741). From v1.4.4, `eth/65` is [disabled by default](https://github.com/hyperledger/besu/pull/741).
The `eth/65` change is not [backwards compatible](https://github.com/hyperledger/besu/issues/723). If enabled, peers will slowly drop off and eventually Besu will fall out of sync or stop syncing.
This has the following impact:
* In a private network, nodes using the 1.4.3 client cannot interact with nodes using 1.4.2 or earlier
clients.
* On mainnet, synchronizing eventually stalls.
A fix for this issue is being actively worked on. A fix for this issue is being actively worked on.
@ -36,12 +40,6 @@ Workaround -> On AWS, a full restart of the AWS VM is required to restart the fa
Fast sync is not currently supported on Digital Ocean. We are investigating options to Fast sync is not currently supported on Digital Ocean. We are investigating options to
[add support for fast sync on Digital Ocean](https://github.com/hyperledger/besu/issues/591). [add support for fast sync on Digital Ocean](https://github.com/hyperledger/besu/issues/591).
## Bootnodes must be validators when using onchain permissioning
- Onchain permissioning nodes can't peer when using a non-validator bootnode [\#528](https://github.com/hyperledger/besu/issues/528)
Workaround -> When using onchain permissioning, ensure bootnodes are also validators.
## Privacy users with private transactions created using v1.3.4 or earlier ## Privacy users with private transactions created using v1.3.4 or earlier
A critical issue for privacy users with private transactions created using Hyperledger Besu v1.3.4 A critical issue for privacy users with private transactions created using Hyperledger Besu v1.3.4

Loading…
Cancel
Save