Test Details Overview

Let a forced block join the election already running for its root (#5251)

active_elections::insert asserted that an election found for the block's root already contains the block. That holds while the only thing replacing a root's ledger successor is an election forcing its own winner, but the process RPC can force any block: the forced block rolls the successor back, the rollback observer keeps that root's election, and the scheduler then activates a block its election has never seen. Debug builds hit the assert, release builds leave the election voting on the rolled back block alone.

The assert goes, and the processed-blocks observer treats a forced block that landed like a fork result, so handle_fork hands it to the running election through the same path and the fork cache covers an election started in between.

__________

Type: commit

Hash: 059ca47cb008cd31e414321d594fc3e254e9ace7

Created: yesterday

__________

gr0v1ty/nano-node:059ca47cb008cd31e414321d594fc3e254e9ace7