This repository was archived by the owner on Jul 27, 2022. It is now read-only.
Problem: integration test doesn't use tx-query (CRO-618)#637
Merged
bors[bot] merged 1 commit intocrypto-com:masterfrom Dec 6, 2019
Merged
Problem: integration test doesn't use tx-query (CRO-618)#637bors[bot] merged 1 commit intocrypto-com:masterfrom
bors[bot] merged 1 commit intocrypto-com:masterfrom
Conversation
Contributor
Author
|
bors try |
Contributor
tryBuild failed |
Contributor
Author
|
bors retry |
calvinaco
approved these changes
Nov 28, 2019
Contributor
tryBuild failed |
Codecov Report
@@ Coverage Diff @@
## master #637 +/- ##
=========================================
+ Coverage 70.17% 70.57% +0.4%
=========================================
Files 133 133
Lines 16384 16369 -15
=========================================
+ Hits 11497 11553 +56
+ Misses 4887 4816 -71
|
Contributor
Author
|
bors retry |
Contributor
tryBuild failed |
calvinaco
suggested changes
Nov 28, 2019
Contributor
Author
|
bors retry |
Contributor
tryBuild failed |
Contributor
Author
|
bors retry |
Contributor
tryBuild failed |
Contributor
Author
|
bors retry |
Contributor
tryBuild failed |
Contributor
Author
|
bors retry |
Contributor
tryMerge conflict |
Contributor
Author
|
bors retry |
Contributor
Author
|
bors retry |
Contributor
tryBuild failed |
Contributor
Author
|
bors retry |
Contributor
tryBuild failed |
Contributor
Author
|
bors try |
Contributor
tryBuild failed |
leejw51crypto
approved these changes
Dec 3, 2019
leejw51crypto
approved these changes
Dec 5, 2019
4cb940e to
8e76331
Compare
Contributor
Author
|
bors try |
Contributor
tryBuild failed |
Contributor
Author
|
bors retry |
Contributor
tryBuild failed |
yihuang
approved these changes
Dec 6, 2019
Solution: - changed chain-abci, client-cli and client-rpc default compilation not to use the complete mock - added decryption in tx-validation by default - extended client-rpc with mock feature for transaction obfuscation - added dockerfile etc. for tx-query - extended integration test setup + drone pipeline fixed client tx checking and generation: - only send txids of transactions that are relevant to enclaves - don't generate withdraw transaction if staked state isn't unbonded NOTE: transaction confidentiality is still WIP -- currently data is sealed with a static key known at compile time (rather than some enclave-only random secret that's periodically re-generated by validators' bootstrapping enclaves), so it's still a "mock", but better in the sense that client workflows are more realistic / closer to the complete implementation (decryption queries are over attested TLS to the tx-query enclave rather than plain abci query)
1019649 to
2952ac4
Compare
Contributor
Author
|
bors r+ |
bors bot
added a commit
that referenced
this pull request
Dec 6, 2019
637: Problem: integration test doesn't use tx-query (CRO-618) r=tomtau a=tomtau Solution: - changed chain-abci, client-cli and client-rpc default compilation not to use the complete mock - added decryption in tx-validation by default - extended client-rpc with mock feature for transaction obfuscation - added dockerfile etc. for tx-query - extended integration test setup + drone pipeline NOTE: transaction confidentiality is still WIP -- currently data is sealed with a static key known at compile time (rather than some enclave-only random secret that's periodically re-generated by validators' bootstrapping enclaves), so it's still a "mock", but better in the sense that client workflows are more realistic / closer to the complete implementation (decryption queries are over attested TLS to the tx-query enclave rather than plain abci query) Co-authored-by: Tomas Tauber <2410580+tomtau@users.noreply.github.com>
Contributor
Author
|
oops -- integration test is still executed on Travis: https://travis-ci.org/crypto-com/chain/jobs/621480585?utm_medium=notification&utm_source=github_status so this will require some work -- some flag for travis and compiling with |
Contributor
Contributor
Author
|
or disable integration test on Travis? it seems to ignore it |
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: transaction confidentiality is still WIP -- currently data is sealed with a static key known at compile time
(rather than some enclave-only random secret that's periodically re-generated by validators' bootstrapping enclaves),
so it's still a "mock", but better in the sense that client workflows are more realistic / closer to the complete implementation
(decryption queries are over attested TLS to the tx-query enclave rather than plain abci query)