-
Notifications
You must be signed in to change notification settings - Fork 466
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
go-algorand 3.22.0-stable Release PR #5925
Merged
algojohnlee
merged 34 commits into
algorand:rel/stable
from
Algo-devops-service:relstable3.22.0
Feb 1, 2024
Merged
go-algorand 3.22.0-stable Release PR #5925
algojohnlee
merged 34 commits into
algorand:rel/stable
from
Algo-devops-service:relstable3.22.0
Feb 1, 2024
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
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## rel/stable #5925 +/- ##
==============================================
+ Coverage 56.39% 56.41% +0.01%
==============================================
Files 481 482 +1
Lines 67457 67664 +207
==============================================
+ Hits 38045 38175 +130
- Misses 26851 26922 +71
- Partials 2561 2567 +6 ☔ View full report in Codecov by Sentry. |
algorandskiy
approved these changes
Jan 31, 2024
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.
Overview
This release includes networking optimization improvements, as well as starts laying the groundwork for non-archival relays.
Note: in this release, NetAddress will no longer automatically mark a node as archival, so if you were relying solely on NetAddress for this, you should also set
Archival: true
in your configuration before applying the upgrade. This is a rare configuration, but if you only had NetAddress set, this release will progressively delete blocks from your database until the node only has recent blocks (probably over multiple days while staying caught up to the chain). The sqlite database will not reclaim this disk automatically, so you may want to run a vacuum after it's complete by shutting down the node and running:sqlite3 data/mainnet-v1.0/ledger.block.sqlite "VACUUM"
If you intend to become non-archival (formerly as an archival node), your best path forward is a fresh install.
What's New
Changelog
Enhancements
Bugfixes
any
as constant int inloads
,stores
(#5884)Protocol Upgrade
This release does not contain a protocol upgrade.
NOTE
vFuture changes are not yet available in MainNet or TestNet but can be used in private networks.
Additional Resources