Fixed in 541d13b4cc69a15ae3767499e19e99455064506e. I'm pretty sure I'm seeing the behavior in nakamoto testnet (which I don't think is running that patch), but I need to investigate further to confirm:
| | 2024-09-27T15:22:26.613746583Z - Cycle #80 Signer #1: Block proposal invalid |
| | 2024-09-27T15:22:26.61367519Z - Miner block proposal contains a tenure change, but we've already signed a block in this tenure. Considering proposal invalid. |
| | 2024-09-27T15:22:26.611946469Z - Cycle #80 Signer #0: Block proposal invalid |
| | 2024-09-27T15:22:26.611832519Z - Miner block proposal contains a tenure change, but we've already signed a block in this tenure. Considering proposal invalid. |
| | 2024-09-27T15:22:26.611059779Z - Cycle #80 Signer #3: Block proposal invalid |
| | 2024-09-27T15:22:26.610965315Z - Miner block proposal contains a tenure change, but we've already signed a block in this tenure. Considering proposal invalid.
Fixed in 541d13b4cc69a15ae3767499e19e99455064506e. I'm pretty sure I'm seeing the behavior in nakamoto testnet (which I don't think is running that patch), but I need to investigate further to confirm: