-
Notifications
You must be signed in to change notification settings - Fork 283
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test(e2e): multiple accounts, same encryption key #1137
Conversation
a1ba34d
to
39608d3
Compare
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.
LGTM!
abi: ContractAbi, | ||
args: any[], | ||
encryptionPrivateKey: Buffer, | ||
useProperKey: boolean, |
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.
This parameter is very specific to the account contract e2e tests. I'm fine keeping it in the extracted util for now, but we should rethink this interface later.
// First wait until the corresponding RPC server has synchronised the account | ||
const isUserSynchronised = async () => { | ||
return await wallet.isAccountSynchronised(owner); | ||
}; | ||
await retryUntil(isUserSynchronised, owner.toString(), 5); |
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.
Curious if we actually need this, since we only have 1 rpc server on this test
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.
I looked into the code and it really doesn't seem to be needed here because when tx is mined it is ensured that all the notes were already processed. I removed the check in 0b4aa5a. Thanks
Description
Fixes #1061
Checklist: