merge latest EOS v2.0.5 tag #147
Merged
Conversation
This file contains hidden or 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
remove each
…ith trace-rpc-abis or neither is present
update usage
…lerplate Trace API Plugin and configuration scaffolding
fix issue EOSIO#8582
Improve `create account` description
Add Incoming-defer-ratio description - 2.0
…race-api-extraction-2.0
Fix other blocks.log callout - 2.0
Improve create account description - 2.0
…_create_* methods to allow file to be created.
…` is present IFF a data handler can process the data
… transaction traces. Removed context free action traces to avoid confusion by users. Report input transaction id for onerror transaction trace since that is the id the user knows.
…ng trace not create a trace file. Also, some other cleanup and removed test checks that were enforcing non-invariants.
Trace api extraction - onerror test
Change action data handling and output
Move to new store provider interface
…ead-api migrate response subsystem to the new store read API
…d is not updated at time of signal
llvm 10 support for EOS VM OC - 2.0
…etic Replace bc with shell arithmetic - 2.0
plugin_test fails if core symbol is diferent from 4,SYS
When called without any parameter to override the block size, '/bin/df' uses the $BLOCKSIZE environment variable. That variable may contain units like K, M, G, etc. Before this commit, general.sh took the value of $BLOCKSIZE from the output of 'df' and used it in arithmetic expressions, which broke them because of the unit suffixes. This commit adds the higly portable '-k' option to the 'df' invocation to explicitly set the value of block size to 1024.
tests/get_table_tests.cpp: incorrect use of CORE_SYM_STR - 2.0
Make /bin/df ignore $BLOCKSIZE
…ION_TEST='false' regardless of build type
### With FORCE_LINUX=true, you can run the Docker version in `build.sh` an `package.sh` scripts When running the scripts from Mac OS X, it was always picking up the Darwin conditional paths in the script. `FORCE_LINUX=true` can be used on a Mac OS X environment to run the scripts. ### Fix shell expansion in `package.sh` In the packaging script, there is a Docker pre command that add executable bit permission on *.sh scripts in the `build/packages` folder. However, without the escaping, the shell expansion was performed in the `package.sh` script execution directly instead of being delayed so that the expansion is performed inside the `docker run` call! I suspect this worked in your CI system because execution of `package.sh` in performed in such way that filesystem layout of `package.sh` and filesystem layout of `docker run` were the same and as such, the expanded `chmod 755 file1.sh file2.sh` command was correctly working inside the container. The shell expansion via the `*` is now escaped which correctly delays the expansion until it's in the `docker run` execution environment. ### Conditional buildkite-agent upload Now, the upload task is performed only if BUILDKITE env is set to `true`, so it's possible to run the script without having to upload the actual package.
Add possibility to run .cicd scripts from different environments (2.0.x Backport)
Fix SHIP block delay - 2.0
Support Running ALL Tests in One Build
EOS-VM memory access fix Co-Authored-By: Steven Watanabe steven.watanabe@block.one
Consolidated Security Fixes for 2.0.5
Bump version to 2.0.5
Merge release 2.0.5 to master
* min_activated_stake was changed because it broke unitests
Alladin9393
force-pushed
the
develop-v2.0.5
branch
from
a9d7fc4 to
8e8130a
Compare
roman-tik
approved these changes
Apr 28, 2020
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.
Change Description
Consensus Changes
API Changes
Documentation Additions