-
Notifications
You must be signed in to change notification settings - Fork 493
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.6.0-beta Release PR #3934
go-algorand 3.6.0-beta Release PR #3934
Conversation
AllowV4InnerAppls also means that apps can not perform an inner opt-in to apps with <v4 CSP (since they might then be locked in). And no app can downgrade, as that is a straightforward rule to prevent an app from lowering its CSP and locking other apps into it. The DoubleLedger does a lot of double checking on ledgers produced by rerunning transactions after creating blocks, deserializing the txns from the block and validating the results. testConsensusRange makes it easy for ledger tests to test behavior in many protocol levels. A particular problem it handles is that test can be written to run from some consensus version and in every subsequent version. So if we change behavior in a new version, we'll find out. Co-authored-by: algochoi <[email protected]>
In order to run private networks in docker, it is convenient to mount the data directory. By disallowing the network directory to exist it is not possible to mount the node directory.
arm32 has int32 fields in Timespec struct, but Nanoseconds() returns int64. The new arm32-specific implementation of NanoSleep casts it to int32 as Timespec expects.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks reasonable. Leaving a note to validate my assumption. If incorrect, let me know.
I see vFuture added to AVM: vFuture: inner appls can call v4. Presumably the intent is to highlight that the capability won't be enabled until the next consensus upgrade.
Yup. I just added in the vFuture note in the description on the bottom of the release notes for clarity. |
Build: Update build image from arm32v6 to arm32v7 (#3933) does drop ARM32v6 support, i.e. Raspberry Pi v1 users. Should we/how should we call this out in the release notes? |
Overview
Maintenance release of incremental enhancements and fixes.
What's New
Changelog
New Features
Enhancements
fillBytes
method in ABI and eval.go implementation (#3856)Bugfixes
Other
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