- 09 8月, 2018 2 次提交
-
-
由 Bart Wyatt 提交于
-
由 Bart Wyatt 提交于
- dont add transactions to dedup if they will expire before replay ends - dont do various checks that cannot fail inside trx_context
-
- 08 8月, 2018 12 次提交
-
-
由 Kevin Heifner 提交于
Gh#4836 signals
-
由 Kevin Heifner 提交于
Port 1.1.4 to develop
-
由 Bart Wyatt 提交于
-
由 wanderingbort 提交于
Release 1.1.4
-
由 wanderingbort 提交于
bump version to 1.1.4
-
由 wanderingbort 提交于
Consolidated Security Fixes for 1.1.4
-
由 wanderingbort 提交于
Backport of `fix/asset_mult_and_div` onto `release/1.1.x`
-
由 Bart Wyatt 提交于
- Various regression/unit tests Co-authored-by: NKevin Heifner <heifner_k@ociweb.com> Co-authored-by: NMatt Witherspoon <32485495+spoonincode@users.noreply.github.com>
-
由 Bucky Kittinger 提交于
Update asset.hpp
-
由 wanderingbort 提交于
Update asset.hpp
-
由 Kevin Heifner 提交于
-
由 Bucky Kittinger 提交于
-
- 07 8月, 2018 13 次提交
-
-
由 Bucky Kittinger 提交于
-
由 Bucky Kittinger 提交于
-
由 Bucky Kittinger 提交于
update crypto.h to use const char*
-
由 Bart Wyatt 提交于
-
由 wanderingbort 提交于
remove producer-subjectivness from leeway
-
由 wanderingbort 提交于
make scheduled transactions subjectively fail on tx_cpu_usage_exceeded
-
由 Kevin Heifner 提交于
-
由 Kevin Heifner 提交于
-
由 Bucky Kittinger 提交于
-
由 Bart Wyatt 提交于
producer plugin was treating leeway cpu exceptions as subjective which in turn implies to the rest of the producer code that the block is exhausted. However, this exception rarely clears in a fresh block (only on wall-clock wobble) so it is in-appropriate for the producer plugin to consider this "subjective"
-
由 Kevin Heifner 提交于
Update README.md
-
由 Kevin Heifner 提交于
-
由 Bart Wyatt 提交于
-
- 06 8月, 2018 2 次提交
-
-
由 Bart Wyatt 提交于
in EOSIO/eos#5001 the ability to bill appropriate CPU time for `soft_fail` and `hard_fail` scheduled transaction was added. However, this exposes an ambiguity in the block structure: There is no way to represent the objective failure of a scheduled transaction due to this limit. This is because the measurement is subjective and must be strictly less than or equal to this limit otherwise the _block_ is objectively bad. As a result, producers will no longer include those scheduled transactions in their blocks, giving each producer a chance to execute it in under the limited time or to another objective failure case. Previous versions of `nodeos` were producing 0 values for billed transaction time which did not resolve the ambgiuity but shifted the failure mode from the desired mode (transaction exceeded an objective maximum) to a different failure mode (transaction under the minimum billable time) allowing those blocks to validate correctly despite the mismatch. resolves EOSIO/eos#5057
-
由 Kevin Heifner 提交于
-
- 04 8月, 2018 11 次提交
-
-
由 Kevin Heifner 提交于
Add filter-out history config option
-
由 Kevin Heifner 提交于
Merge 1.1.3 into develop
-
由 arhag 提交于
Version 1.1.3
-
由 wanderingbort 提交于
bump version to 1.1.3
-
由 arhag 提交于
Fix for #4986 and proper CPU billing for soft_fail and hard_fail
-
由 Bart Wyatt 提交于
-
由 arhag 提交于
-
由 arhag 提交于
-
由 arhag 提交于
-
由 Kevin Heifner 提交于
Enable multi-threading when building boost libraries
-
由 Kevin Heifner 提交于
Pin macos build script to boost 1.67
-