This repository was archived by the owner on Jul 27, 2022. It is now read-only.
Problem: no transaction type for joining validator set (CRO-553)#591
Merged
bors[bot] merged 1 commit intocrypto-com:masterfrom Nov 19, 2019
Merged
Conversation
Codecov Report
@@ Coverage Diff @@
## master #591 +/- ##
==========================================
+ Coverage 67.32% 67.89% +0.57%
==========================================
Files 125 128 +3
Lines 14675 15114 +439
==========================================
+ Hits 9880 10262 +382
- Misses 4795 4852 +57
|
a2f8787 to
987d142
Compare
tomtau
commented
Nov 18, 2019
Solution: - consolidated ABCI node state to have one field dedicated to validate state tracking - added a NodeJoinTx type + basic validation code and tests - added a End block handling when the validator power changed or new nodes were changed -- based on the top validators after modifications, it computes the validator updates it needs to pass to tendermint - small steps in storage/tx.rs refactoring -- two verify functions to distinguish between abci-only and enclave-dependant transactions + moved out the huge functionality tests into a separate file
987d142 to
0ea3ae7
Compare
Contributor
Author
|
bors try |
devashishdxt
approved these changes
Nov 18, 2019
Contributor
Author
|
bors r+ |
Contributor
Merge conflict (retrying...) |
bors bot
added a commit
that referenced
this pull request
Nov 18, 2019
591: Problem: no transaction type for joining validator set (CRO-553) r=tomtau a=tomtau Solution: - consolidated ABCI node state to have one field dedicated to validate state tracking - added a NodeJoinTx type + basic validation code and tests - added a End block handling when the validator power changed or new nodes were changed -- based on the top validators after modifications, it computes the validator updates it needs to pass to tendermint - small steps in storage/tx.rs refactoring -- two verify functions to distinguish between abci-only and enclave-dependant transactions + moved out the huge functionality tests into a separate file NOTE: don't get scared about the PR size -- most of it is just moving `storage/tx.rs` tests into a separate file (it'll still need some improvements, but that can be done in a separate PR) 593: Problem: (CRO-582) Create transfer address is not re-usable r=tomtau a=calvinlauco Solution: Extracted MultiSigAddress from root_hash service to serve single responsibility --- Remarks: - This PR is a pre-requisite of the JS library by making components re-usable by JS - Removed n(total_signers) field because it is implied from len of public keys Co-authored-by: Tomas Tauber <2410580+tomtau@users.noreply.github.com> Co-authored-by: Calvin Lau <calvinlauco@gmail.com>
Contributor
tryBuild failed |
Contributor
Build failed (retrying...) |
bors bot
added a commit
that referenced
this pull request
Nov 18, 2019
591: Problem: no transaction type for joining validator set (CRO-553) r=tomtau a=tomtau Solution: - consolidated ABCI node state to have one field dedicated to validate state tracking - added a NodeJoinTx type + basic validation code and tests - added a End block handling when the validator power changed or new nodes were changed -- based on the top validators after modifications, it computes the validator updates it needs to pass to tendermint - small steps in storage/tx.rs refactoring -- two verify functions to distinguish between abci-only and enclave-dependant transactions + moved out the huge functionality tests into a separate file NOTE: don't get scared about the PR size -- most of it is just moving `storage/tx.rs` tests into a separate file (it'll still need some improvements, but that can be done in a separate PR) Co-authored-by: Tomas Tauber <2410580+tomtau@users.noreply.github.com>
Contributor
Build failed |
Contributor
Author
|
bors r+ |
bors bot
added a commit
that referenced
this pull request
Nov 18, 2019
591: Problem: no transaction type for joining validator set (CRO-553) r=tomtau a=tomtau Solution: - consolidated ABCI node state to have one field dedicated to validate state tracking - added a NodeJoinTx type + basic validation code and tests - added a End block handling when the validator power changed or new nodes were changed -- based on the top validators after modifications, it computes the validator updates it needs to pass to tendermint - small steps in storage/tx.rs refactoring -- two verify functions to distinguish between abci-only and enclave-dependant transactions + moved out the huge functionality tests into a separate file NOTE: don't get scared about the PR size -- most of it is just moving `storage/tx.rs` tests into a separate file (it'll still need some improvements, but that can be done in a separate PR) Co-authored-by: Tomas Tauber <2410580+tomtau@users.noreply.github.com>
Contributor
Build failed |
Contributor
Author
|
bors retry |
bors bot
added a commit
that referenced
this pull request
Nov 19, 2019
591: Problem: no transaction type for joining validator set (CRO-553) r=tomtau a=tomtau Solution: - consolidated ABCI node state to have one field dedicated to validate state tracking - added a NodeJoinTx type + basic validation code and tests - added a End block handling when the validator power changed or new nodes were changed -- based on the top validators after modifications, it computes the validator updates it needs to pass to tendermint - small steps in storage/tx.rs refactoring -- two verify functions to distinguish between abci-only and enclave-dependant transactions + moved out the huge functionality tests into a separate file NOTE: don't get scared about the PR size -- most of it is just moving `storage/tx.rs` tests into a separate file (it'll still need some improvements, but that can be done in a separate PR) Co-authored-by: Tomas Tauber <2410580+tomtau@users.noreply.github.com>
Contributor
bors bot
added a commit
that referenced
this pull request
Dec 5, 2019
653: Bump serde_json from 1.0.42 to 1.0.44 r=tomtau a=dependabot-preview[bot] Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.42 to 1.0.44. <details> <summary>Release notes</summary> *Sourced from [serde_json's releases](https://github.com/serde-rs/json/releases).* > ## v1.0.44 > - Implement IntoDeserializer for serde_json::Value to allow deserializing from types like `HashMap<String, Value>` ([#591](https://github-redirect.dependabot.com/serde-rs/json/issues/591)) > > ## v1.0.43 > - Declare accurate minimum required version of indexmap crate when preserve-order feature is enabled ([#590](https://github-redirect.dependabot.com/serde-rs/json/issues/590), thanks [@​nlordell](https://github.com/nlordell)) </details> <details> <summary>Commits</summary> - [`1977e69`](serde-rs/json@1977e69) Release 1.0.44 - [`9f13db7`](serde-rs/json@9f13db7) Merge pull request 591 from erickt/value-into-deserializer - [`4ae13a5`](serde-rs/json@4ae13a5) Implement IntoDeserializer for Value - [`f7a4da0`](serde-rs/json@f7a4da0) Release 1.0.43 - [`76b2366`](serde-rs/json@76b2366) Merge pull request [#590](https://github-redirect.dependabot.com/serde-rs/json/issues/590) from nlordell/bump_indexmap_version - [`19ba7be`](serde-rs/json@19ba7be) fix required minimum indexmap version - See full diff in [compare view](serde-rs/json@v1.0.42...v1.0.44) </details> <br /> [](https://dependabot.com/compatibility-score.html?dependency-name=serde_json&package-manager=cargo&previous-version=1.0.42&new-version=1.0.44) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired) </details> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com>
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Solution:
NOTE: don't get scared about the PR size -- most of it is just moving
storage/tx.rstests into a separate file (it'll still need some improvements, but that can be done in a separate PR)