-
Notifications
You must be signed in to change notification settings - Fork 863
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updated known issues for 1.4.6 #996
Updated known issues for 1.4.6 #996
Conversation
Signed-off-by: Madeline <madeline.murray@consensys.net>
CHANGELOG.md
Outdated
|
||
#### Previously identified known issues | ||
|
||
- [Eth/65 not backwards compatible](KNOWN_ISSUES.md#eth65-not-backwards-compatible) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The backwards incompatibility part of ETH/65 is fixed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated
CHANGELOG.md
Outdated
@@ -31,7 +31,19 @@ The [1.5 release](docs/1_5_Upgrade.md) is scheduled for early July. | |||
|
|||
### 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. Fixes issue where `eth_getLogs` queries that were too large or too broad | |||
could cause Besu to crash. [\#986](https://github.com/hyperledger/besu/pull/986) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Besu can still crash/hang, that's the deeper fix we mentioned.
could cause Besu to crash. [\#986](https://github.com/hyperledger/besu/pull/986) | |
never return. [\#986](https://github.com/hyperledger/besu/pull/986) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed and added the known issue back. Thanks for catching my miss.
Signed-off-by: Madeline <madeline.murray@consensys.net>
Signed-off-by: Madeline <madeline.murray@consensys.net>
Fast Sync has always worked for us on AWS? curious, just literally spun up an instance and tried using the 1.4.6-rc1 and was able to fast sync on AWS |
* Updated known issues Signed-off-by: Madeline <madeline.murray@consensys.net> Signed-off-by: Sally MacFarlane <sally.macfarlane@consensys.net>
Updated known issues for 1.4.6