mirror of
https://github.com/bigchaindb/bigchaindb.git
synced 2024-06-25 18:56:44 +02:00
e6893632dc
* Problem: We need a way to synchronize a halt to block production to allow for upgrades across breaking changes. * Solution: Created `MigrationElection`. * Problem: Need documentation for `migration` elections. * Solution: Updated the docs. * Problem: `MigrationElection` needs 'new' CLI method. * Solution: Updated the definition of `election` to include the new `migration` type. * Problem: The way `end_block` checks for concluded elections assumes there is only one type of election (so we can't conclude an `upsert-validator` and a `chain-migration` at the same height). * Solution: Re-engineered the code in `Elections` to conclude multiple elections in the same block. If more than one election change the validator set, only one of them is applied. * Problem: Tendermint change to store validator changes at height h+2 will break `Election.get_status`. * Solution: Reworked `get_validator_change` to look at only the latest block height or less.
10 lines
440 B
Python
10 lines
440 B
Python
from bigchaindb.migrations.chain_migration_election import ChainMigrationElection
|
|
|
|
|
|
def test_valid_migration_election(b_mock, node_key):
|
|
voters = ChainMigrationElection.recipients(b_mock)
|
|
election = ChainMigrationElection.generate([node_key.public_key],
|
|
voters,
|
|
{}, None).sign([node_key.private_key])
|
|
assert election.validate(b_mock)
|