-
Notifications
You must be signed in to change notification settings - Fork 490
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
Onetechnical/relbeta2.1.0 #1347
Merged
algojohnlee
merged 375 commits into
algorand:rel/beta
from
onetechnical:onetechnical/relbeta2.1.0
Aug 4, 2020
Merged
Onetechnical/relbeta2.1.0 #1347
algojohnlee
merged 375 commits into
algorand:rel/beta
from
onetechnical:onetechnical/relbeta2.1.0
Aug 4, 2020
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
…ages-script The gpg-fake script was recently moved, but the path was incorrectly updated.
python3.7-venv turned into python3.8-venv in ubuntu 20.04, use the default version instead.
Now that the protocol upgrade fixing the bug has gone through, we no longer need to keep the buggy version around for compatibility.
The script to configure dev dependencies installs various supporting golang modules. However, these versions do not take into account entries in go.mod, which means the versions can conflict. This is a restoration of a previous pull request, with the bug fix around handling error conditions.
The connectionPerformanceMonitor is suspected to slow down critical communication paths. I was able to optimize it further and it looks now quite decent. ( i.e. 170Kns->6Kns ) The reminder of the 5Kns is mainly attributed to the deadlock locking logic, which I'm inclined to change in the PR unless proven it's really needed.
The test was creating a proxy which delays requests execution as a way to slow down the catchpoint catchup process. This is important so that we can monitor from the goal command that the catchup is working as intended. However, delaying the command execution caused an issue where the node was trying to issue multiple requests for blocks 1-16, in parallel, which reached the proxy at an arbitrary order. As a result, the request for block #1 was delayed by more than 4 second, causing it it timeout. The solution was to reconfigure the number of parallel blocks being retrieved to 2. This would ensure that we only getting two blocks at a time. Since the delay is configured to 1.5 seconds, this would also be the delay, which is well under 4 second.
TestCatchupOverGossip was using an incorrect verification and shown random failures.
Add an e2e teal/compile endpoint test
Replace references to BUILDCHANNEL with CHANNEL to simplify scripts.
Update the documentation for passing multiple arguments for goal commands, and standardize the usage styling.
This PR adds automatic detection of betanet genesis files and update the DNSBootstrapID if it has not been set by the user. The implementation follow the same logic as with devnet, and would allow us to deploy betanet nodes without requiring the end user to provide a config.json file which sets the DNSBootstrapID explicitly.
This change reduces the time it takes to execute the TestConnMonitorStageTiming by factor of 14. It's expected to take about 10 seconds on travis, whereas it used to take 150 seconds.
go.mod is now used to specify the go version. Updated go version to 1.12.17
This makes sure that the test build scripts work on arm* architectures. The main change is to test the ARCH variable for some variation of arm* in mule/test/test.sh and will call the run_tests script directly. This bypasses the path that amd64 builds take, which is to further spin up more docker containers and run the run_tests in each of them. I feel this is unnecessary for arm*, and further the run_tests script initiates all the tests that all architectures must run. The rest (and the majority) of the changes were necessary to allow the run_tests shell script to be called directly. These changes now have each shell script determine the values which it needs rather than having them passed from a Makefile. This is better practice and is inline with what is being done in the indexer project, as well.
Implement Algorand applications, as specified in algorandfoundation/specs#30.
This change fixes a presumed typo.
A program with no #pragma version 2 should result in compiling a version 1 program. Co-authored-by: Max Justicz <max@justi.cz>
The catchpointdump utility allows to perform the following: Given a catchpoint file, it knows how to read it's content and dump the output in a human readable format into a separate file. Given a network name and a round number, it would fetch the catchpoint for that round from all the relays of that network, save the catchpoint file, and dump it's content. Given an ledger tracker database, it can dump the database content into a file
Fix a data race in Basic Catchpoint Catchup Test
goal app info is like goal asset info, printing out properties describing an app.
We have found a rare synchronization issue in accountUpdates. The issue is expressed when querying for a balance beyond the MaxBalLookback boundaries, where is can result in providing an incorrect result.
…ture Refactor expect runners by creating a unified expect fixture
…eal-test Extend timeout for stateful teal expect tests
* Update stateful TEAL docs. * Support empty substrings in TEAL. * Foundation feedback * Update asset_params_get
Disallow old TEAL versions for ApplicationCall transactions, disallow groups containing {Apps, RekeyTo} and v0/v1 TEAL
Add created/opted in apps to `goal account list`
Fix a bug where goal inspect fails to process a rekeyed transaction
Testing script for Gossip and TxSync
The next release will update the minor version number. This will move us from 2.0.x to 2.1.x.
"byte 0x" produces empty byte slice and substring also can return empty slice so it is better to be consistent and allow empty literals as well
TEAL: allow empty string literals
…ul_teal Update upgrade path to v24
onetechnical
requested review from
tsachiherman,
bricerisingalgorand,
btoll,
egieseke and
tsachizehub
August 4, 2020 20:28
tsachiherman
approved these changes
Aug 4, 2020
tsachiherman
pushed a commit
to tsachiherman/go-algorand
that referenced
this pull request
Jul 7, 2021
…ta2.1.0 Onetechnical/relbeta2.1.0
PhearZero
pushed a commit
to PhearNet/crypto
that referenced
this pull request
Jan 17, 2025
…ta2.1.0 Onetechnical/relbeta2.1.0
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.
Summary
Highlights
Changes
txn.ForeignAssets
field/teal
end points disabled by default #1109)goal account list
TealKeyValue
,EvalDeltaKeyValue
modelgoal multisig sign
fails if sender rekeyed to multisig address #1238)TxnRoot
for block 0ApplyData.EvalDelta
is clear ifapplyEvalDelta
failsProtocol Upgrade
This release contains a consensus protocol upgrade, which implements the following spec:
https://github.com/algorandfoundation/specs/tree/3a83c4c743f8b17adfd73944b4319c25722a6782
Other Notes
A database migration is included this release, which will add a one-time startup delay of 2-10 seconds. This is for re-encoding of the accounts database, if needed. Note: the database schema will remain compatible with the previous release.
Additional Resources
Test Plan
N/A