go-algorand 3.5.0-beta #3719
Merged
go-algorand 3.5.0-beta #3719
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
go-algorand 3.4.2-stable
) ## Summary Provides a pointer to instructions added in algorand/indexer#906 for updating Indexer E2E test input. ## Test Plan N/A - Changes docs. Though I expect to trial the instructions as discussed in algorand/indexer#906.
…4.2-remerge go-algorand relstable3.4.2-remerge
## Summary This PR adds support of for unlimited assets. Done: - [x] Update this title - [x] Complete & Merge the implementation of the accounts prefetched during the validation (algorand#3666) - [x] Create & Merge a spec update ( algorandfoundation/specs#62 (comment) ) - [x] Create & Merge a consensus upgrade (algorand#3674) ## Test Plan Extend, update and add new unit tests.
## Summary Refactored WriteThread such that it'll be easier to add new operations. Didn't delete the DBs`inner` functions, instead moved them to be handled by a struct that implements `dbOp` interface
…tion (algorand#3707) ## Summary Follow-on to algorand#3702, the copy-pasted code in AccountApplicationInformation was checking the wrong value before returning AppParams.
## Summary This adds configuration options to adjust the sizes of buffered channels used by the agreement system for incoming messages. ## Test Plan Existing tests should pass.
…ails message (algorand#3703) ## Summary This pulls a bit of code from the the [pipelining branch](https://github.com/algorand/go-algorand/tree/feature/pipeline) to add a "validatedAt" duration field to the agreement.proposal type. This is used to provide an extra field in the BlockAcceptedEventDetails message describing how soon into the round each block was validated. ## Test Plan Existing tests should pass, and a new test might be helpful to show that the value is getting filled in correctly.
Summary The existing code was failing the fast catchup on node startup if the peers could not be retrieved from the network package. Unfortunately, this is almost always the case. This change allow the node to retry fetching the peers list from the network package multiple times, while having a short delay between the iterations. This issue was reported by a Algorand Forum member. Test Plan Test the change manually.
…nd#3710) ## Summary The TestAssetConfig was not updated correctly to support unlimited assets. This PR brings it up to date, as well as improve the runtime of the test. ## Test Plan Use Circle-CI.
## Summary Similar to algorand#1938 this adds the TagCounter to report message counters by type. It also removes labels from the existing Counters, which should improve their performance. ## Test Plan Existing tests should pass.
…lgorand#3708) ## Summary This replaces the various Ledger interfaces' `LookupResource` method with two more specific `LookupApplication` and `LookupAsset` methods. Following up on code review feedback from algorand#3652. ## Test Plan Existing tests should pass, including the ones that implement their own mock ledger.
## Summary There was one Clock implementation not updated in algorand#3703 in the agreement fuzzer testing package's NetworkFacade type. This updates it to fully implement the Clock interface.
## Summary The `satori/go.uuid` dependency was reported to contain a vulnerability ( https://nvd.nist.gov/vuln/detail/CVE-2021-3538#VulnChangeHistorySection ). While this vulnerability would have no negative impact on the Algorand blockchain, it does mislead automated vulnerability detectors and points the Algorand codebase to be considered insecure. Given that this package was used in so few locations, and in such a small scope, I have removed the usage of it completely. Instead, I have implemented a random UUID which would work correctly for our needs. ## Test Plan Unit tests added.
Codecov Report
@@ Coverage Diff @@
## rel/beta #3719 +/- ##
============================================
- Coverage 49.92% 49.57% -0.35%
============================================
Files 382 392 +10
Lines 64411 68588 +4177
============================================
+ Hits 32158 34004 +1846
- Misses 28817 30845 +2028
- Partials 3436 3739 +303
Continue to review full report at Codecov.
|
algojack
approved these changes
Mar 7, 2022
PhearZero
pushed a commit
to PhearNet/crypto
that referenced
this pull request
Jan 17, 2025
go-algorand 3.5.0-beta
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.
What's New
Protocol Upgrade
This release contains a protocol upgrade.
Changelog
Enhancement
Additional Resources