go-algorand 3.16.0-beta Release PR #5406
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Bob Broderick <[email protected]> Co-authored-by: Hang Su <[email protected]>
Nodes aggregate and save state proof information to be able to recover a stalled state proof subchain. In case of a problem nodes will not lose old state proof data so it will be possible to recover the stalled state proof chain. Data being saved: * state proof builder state is persisted * a new state proof verification tracker also persists some state proof related data from block headers Co-authored-by: Or Aharonee <[email protected]> Co-authored-by: Almog Tal <[email protected]> Co-authored-by: Jonathan Weiss <[email protected]> Co-authored-by: Pavel Zbitskiy <[email protected]>
Add a `/ready` readiness probe endpoint for kubernetes deployments
Co-authored-by: cce <[email protected]>
Codecov Report
@@ Coverage Diff @@
## rel/beta #5406 +/- ##
============================================
+ Coverage 53.57% 55.44% +1.87%
============================================
Files 430 452 +22
Lines 54130 63826 +9696
============================================
+ Hits 28998 35389 +6391
- Misses 22889 26009 +3120
- Partials 2243 2428 +185
... and 346 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
jsgranados
requested review from
winder,
jannotti,
onetechnical,
gmalouf,
icorderi,
algorandskiy and
bbroder-algo
gmalouf
approved these changes
May 22, 2023
gmalouf
approved these changes
May 22, 2023
There was a problem hiding this comment.
I guess all of these should go into Bugfix section.
Tests: Fix State-Proofs ledger tests (https://github.com/algorand/go-algorand/pull/5379)
Tests: Fix error messages in ledger tests (https://github.com/algorand/go-algorand/pull/5363)
Tests: fix consensus version inconsistency in newTestLedger (https://github.com/algorand/go-algorand/pull/5342)
Tests: Fix devmode test (https://github.com/algorand/go-algorand/pull/5334)
All links [here] are placeholders (probably fine).
onetechnical
approved these changes
May 23, 2023
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This release requires a protocol upgrade.
This release contains a consensus protocol upgrade, which implements the following spec: https://github.com/algorandfoundation/specs/tree/abd3d4823c6f77349fc04c3af7b1e99fe4df699f
Overview
This update includes a drop in round time of ~0.4 seconds, a robustness improvement to State Proofs, and several developer-oriented features in the AVM, simulate, and devmode.
What's New
/readyendpoint to benefit any K8's deployment as a readiness probe. The endpoint will return a200response code once algod has caught up to the latest state.config.jsonfile. There are also changes to make mounting a data directory more consistent. See DockerHub for more details.Changelog
Protocol Upgrade
This release contains a double protocol upgrade (Consensus v37 and v38). No action is needed from node runners but is called out for transparency. Consensus v37 is a technical upgrade released in unison with Consensus v38. v37 is needed to allow nodes to build up a necessary state to support State Proof related options in consensus v38.
New Features
/readyendpoint) (#4844)Enhancements
submitFormfrom go-sdk PR Add support for travis ARM64 integration tests #335 (#5253)Bugfixes
goal clerk simulate(#5259)ddargument to use a bytes value (#5263)Additional Resources