This repository has been archived by the owner on Sep 26, 2019. It is now read-only.
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.
Clique acceptance tests #290
Clique acceptance tests #290
Changes from all commits
8699cb8
bc2fccf
907739d
3440d5f
5b3aefb
5f76acb
7a7f769
4237915
6eaad43
5dfb9c8
5f3d5bb
a113454
74ba546
73aa666
3be7e0b
d19fa8a
b12e563
7807a18
03f9eae
de5a1e8
ba6a232
af45272
74af4e5
e84e133
83aa0ae
da89fbe
2dd7596
adb87fa
d829065
05cb7ce
e3fd3c9
138e58e
11ca449
044f8a1
40bd5bd
853c403
7af4671
ab01541
cd3451f
5273625
b0cd99f
04dbd3b
9f814f1
219830b
9d35daf
2afe001
478f95c
819d5c5
2689a06
cde87bd
e78b394
cb88863
3863b53
69e93b9
bd5ec67
4178105
026fa0f
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
should this work with 0x2? or does it have to be 3?
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.
We are already at block 1 when vote in the new validator, so it is working after 2 blocks have progressed.
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.
nit: I suspect there's a risk that you haven't actually mined separate blocks - can the test be updated to ensure the transactions are spread across blocks?
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.
The transfers are being done from different nodes so there should be multiple blocks.
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.
Transactions are communicated between nodes. They're only guaranteed to be in different blocks if you wait for their effects to be applied before sending the next transaction. So:
Must be in one block and any transaction sent after that must be in a different block.
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.
Yeah true, fortunately am following that pattern of during the transfer and then waiting for the effects the applied.
So this what is being done atm:
` minerNode1.execute(transactions.createTransfer(sender, 50));
cluster.verify(sender.balanceEquals(50));
So I'm expecting that at least 3 blocks will be created by doing this.