This repository has been archived by the owner on Dec 16, 2021. It is now read-only.
feat!: configure passFakeAssetLockProofForTests
#222
Merged
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.
Issue being fixed or feature implemented
With the local network there is no instant lock quorums atm, so we use fallbacks in Drive and need to pass fake instant lock messages.
What was done?
Introduced
platform.drive.passFakeAssetLockProofForTests
option which is enabled for local config.How Has This Been Tested?
None
Breaking Changes
platform.drive.passFakeAssetLockProofForTests
option is required.Checklist:
For repository code-owners and collaborators only