Release: go-algorand 3.7.0-beta Release PR #4050
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
go-algorand 3.5.1-stable
While upgrading to golang 1.17.9 a couple of race conditions have been detected during E2E tests. This fixes catchpoint label assignment.
In e2e.sh when we fail to set the E2E_PLATFORM variable, the shell will complain that we are using a binary operator (==) on a single argument. Setting the left side of the test statement to a string with variable interpolation fixes this. The e2e python client runner does not initialize the stdout and stderr variables which causes an exception in reportcomms when the except block runs after an exception.
…3949) Running e2e go tests fails when the repo is not cloned inside the GOPATH. This change looks up the current directory using runtime.Caller as an alternative to hard coding the GOPATH location.
Unifies the inner transaction ID calculation with a new consensus parameter, UnifyInnerTxIDs. Co-authored-by: Ben Guidarelli <[email protected]>
Bump go version to 1.17.9 Also includes //+build => //go:build generated via make sanity Fixed some data races discovered by 1.17 race detector
…actions (algorand#3829) Currently, the TxnRoot block header contains the root of the merkle tree built from the transactions in the block, using the SHA512_256 hash function. Since the Ethereum VM (and others) does not support SHA512_256 natively, we have added a new header, which will be used by the Light Clients deployed on other networks in order to verify Algorand blocks. Co-authored-by: algoidan <[email protected]>
Test for a network in transition.
Runs a 6 node network with the following topology:
New Leaf 1 New Leaf 2
> New Relay - Old Relay <
Old Leaf 1 Old Leaf 2
…lgorand#3958) * replace crypto.HashObj(Transaction) with Transaction.ID()
This should ensure make msgp has been run for changes that impact msgp serialization on CI builds. It looks like algorand#3829 was merged but missed changes to agreement/msgp_gen.go and gci updates from algorand/msgp#14 were not incorporated into algorand#3919.
* add simple codecov config * add patch to .codecov.yml
* allow foreign app accounts to be accessed (immutably)
* add bn256 add, scalar multiply and pairing opcode * replace with gnark bn254 and bench * update opcost for bn256 according to benchmark Some doc tweaks, and moved implementation to pairing.go These opcodes should stay in vFuture until 1. We consider the serialization format 2. We have unit tests 3. We consider BLS 12-381 (and the opcodes of eip 2537) 4. Audit of gnark-crypto library Co-authored-by: Bo Yao <[email protected]> Co-authored-by: Bo Yao <[email protected]> Co-authored-by: bo-abstrlabs <[email protected]> Co-authored-by: chris erway <[email protected]>
* make TagCounter metrics easier to use with prometheus * ensure 0 counters are logged * allow for pre-declaring TagCounter tags for use with prometheus * fix expected in TestTagCounterWriteMetric * deregister counter used in test * fix lint warning * CR comment * Log incorrect metrics for debugging test failures * deregister more counters and tagcounters used by tests * remove unused Segment
…Transactions: true (algorand#3918) Save bandwidth by having non-participating non-relay nodes opt-out of TX transaction gossip traffic using message-of-interest. To enable set localConfig.ForceFetchTransactions = true Manual testing has started local private networks to ensure that the new message-of-interest propagated. Cluster tests were run to check bandwidth usage. Co-authored-by: cce <[email protected]>
When generating the CLI documentation for the Developer Portal it was noticed that tealdbg was missing. Much like goal, kmd, and algokey, added the "generate-docs" command option to generate the markdown output.
reseting -> resetting
* add metrics.RuntimeMetrics * hook up EnableRuntimeMetrics as new config variable * set EnableRuntimeMetrics: true in netgoal-generated configs * add EnableRuntimeMetrics to bootstrappedScenario and custom recipes * check that all defaultRuntimeMetrics are supported by current version of go * add TestSanitizePrometheusName * add partitiontest to new tests * use algod_go_ prefix for prometheus runtime metrics
Algo-devops-service
requested review from
algoanne,
algobarb,
algojack,
egieseke,
michaeldiamant and
onetechnical
algolucky
changed the title
Codecov Report
@@ Coverage Diff @@
## rel/beta #4050 +/- ##
============================================
+ Coverage 49.81% 54.49% +4.67%
============================================
Files 409 391 -18
Lines 68897 48665 -20232
============================================
- Hits 34320 26518 -7802
+ Misses 30874 19920 -10954
+ Partials 3703 2227 -1476
Continue to review full report at Codecov.
|
michaeldiamant
approved these changes
May 27, 2022
egieseke
approved these changes
May 31, 2022
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
Bandwidth optimization for non-participating nodes and golang 1.17 upgrade.
What's New
Note
A new flag was added to
update.shthat will enable checksum and signature verification on the downloadedupdaterarchive with the goal that at some point in the future, this will be the default. This requires thatgpgandsha256sumare available on the system to be able to perform the checks. To start using this, pass-verifywhen calling the script. If-verifyis not explicitly passed,update.shwill function the same as before.Changelog
New Features
Enhancements
Bugfixes
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