-
Notifications
You must be signed in to change notification settings - Fork 82
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
Release 2.3.0. #392
Merged
Merged
Release 2.3.0. #392
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
* Implementation for deserialized values from bytes to current or legacy Borsh-encoded parameters for passing to the engine `call` function, and to provide backward type compatibility. * Implementation for deserialized values from bytes to current or legacy Borsh-encoded parameters for passing to the engine `call` function, and to provide backward type compatibility: improved code formatting by `cargo fmt`, addressing notes about bytes order (endianness) in array type conversion to U256 and Wei types, caching bytes returned by `io.read_input()` to prevent double calls for reading register from engine `call()` function during serialization attempts. * Implementation for deserialized values from bytes to current or legacy Borsh-encoded parameters for passing to the engine `call` function, and to provide backward type compatibility: implemented `deserialize()` method for `CallArgs` to follow SOI principles and made code even more clean on engine top level. * Implementation for deserialized values from bytes to current or legacy Borsh-encoded parameters for passing to the engine `call` function, and to provide backward type compatibility: improved implementation of `deserialize()` method for `CallArgs` to suppot Borsh bytes parsing for new structures in call args enum (for future extensibility reason), made new tests for `CallArgs::deserialize()` and for old data structure with legacy arguments, add comments, fix existed tests. * Fix formatting with `cargo fmt` * Fix existing tests; Formatting with `cargo fmt` * Fix naming for call args types.
Bumps [@openzeppelin/contracts](https://github.com/OpenZeppelin/openzeppelin-contracts) from 4.3.2 to 4.3.3. - [Release notes](https://github.com/OpenZeppelin/openzeppelin-contracts/releases) - [Changelog](https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/CHANGELOG.md) - [Commits](OpenZeppelin/openzeppelin-contracts@v4.3.2...v4.3.3) --- updated-dependencies: - dependency-name: "@openzeppelin/contracts" dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]>
Drop automagic math ops Hand write in the boilerplate Complete rest of precompiles Fix clippy issues Fix tests Fmt Better implementation Small fixes Fix tests Add missed gas Feature gate import Remove unnecessary comment. Prep for rebase Remove evm and evm_core from types
Include meta-call feature when running tests Fix imports, include versioning of imports in prelude.
* NEAR random numbers from solidity contract Add Precompile that allows calling random numbers from solidity contracts. * Use randomSeed as name, and update docstring * Remove unused constant * Rename RandomBytes to RandomSeed * Invoke random_seed outside of the engine - Make sure random_seed (from NEAR Runtime) is not called inside the engine. - Refactor all usage of random_seed to use H256 * Fix CI
…th the blockchain (#382)
Revert chain ID for now Change note from betanet to localnet
joshuajbouw
force-pushed
the
release-2.3.0
branch
from
December 10, 2021 10:45
c38d39d
to
c255b9e
Compare
mrLSD
approved these changes
Dec 10, 2021
birchmd
reviewed
Dec 10, 2021
joshuajbouw
force-pushed
the
release-2.3.0
branch
from
December 10, 2021 14:58
c255b9e
to
a5c9141
Compare
artob
reviewed
Dec 10, 2021
### Fixes | ||
|
||
- There was an issue with the original storage not actually being stored. Unfortunately, previous | ||
transactions can't be updated with this change. This has been fixed by [@birchmd]. ([#390]) |
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.
This is a pretty poor description that will not be comprehensible to most anybody who reads this changelog. What is "the original storage"? Cool, old transactions can't be updated--what is the actual impact?
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.
[2.3.0] - 2021-11-10
Added
[@birchmd]. (#368 #297)
Changes
deposit
andft_on_transfer
were changed as they were not attaching enoughgas, as changed by [@mrLSD]. (#389)
Fixes
transactions can't be updated with this change. This has been fixed by [@birchmd]. (#390)
call. This was fixed in a backwards compatible manner by [@andrcmdr], as reported by [@birchmd].
(#351 #309)
ExitToNear
precompile by [@birchmd].(#311)
Removed