Merging latest develop #5089

…e version; instead, immediately re-sync

…hus its maximum time between steps), and raise relayer initiative when there's a new network result

…her thread's prompting

…es if the sortition reward cycle is not equal to our tracked reward cycle

…ess it processes the message completely

…hake first

…wnloader has it on a reward cycle boundary. Don't treat it as an error if the node doesn't have it yet (which it won't, most of the time, except on reward cycle boundaries)

…rovide a menas of loading them back

…r signatures. If we get enough, then put them into the target block's header and upload the signed block to the node

…s from a processed block posted by the signers

…th the signatures we're waiting for, so we can unblock the miner if the block arrives from any signer before their signatures

…not coherent with the canonical tip

…s-network/stacks-blockchain into fix/multi-miner-fixes-jude

…el to avoid clones

…ng an uploaded block, so the coordinator can be woken up if the block is new

…p are reasons to abort mining

…signatures

…ecks

Co-authored-by: wileyj <2847772+wileyj@users.noreply.github.com>

…d lists

…ork/stacks-core into docs/local-mutantion-testing

Co-authored-by: Aaron Blankstein <aaron@hiro.so>

…injection for block-processing after block-broadcast

…tion handling (so the former can be tested in a unit test)

…m-check CI - Remove Unit Tests From Check

* make `not_available_try_again` error in `GetStackers`, and make it transient in the signer binary * make signer binary timeout on retries in client * update signer outer runloop to differentiate between 'not in signer set' and 'have not loaded info yet' * update signer outer runloop to handle errors and non-presence differently in the signer config refresh * update signer outer runloop to perform signer config refresh on the current cycle (if not loaded yet) and on the next cycle (if in prepare phase for the next cycle). This was causing an issue on exactly the first cycle of Nakamoto, because the signer set cannot be loaded for the first cycle until after the prepare phase * update the signer outer runloop to check the node’s block height on event receipt as well * update the testing harnesses to wait and check more appropriately for status checks from signers, etc.

…e at start of prepare phase

…ig, so we can set it in tests

…doesn't have any bearing on whether or not we should keep mining, so don't check it

…g on the nakamoto transition

Fix: Signers CI tests and refresh signer config behaviors

…-define-trait-signature fix: handle empty type_args in define-trait definition

…ting docs & script for running cargo mutants locally on CI limitation

fix: Rust 1.80 warnings

CI: fix mock miner test

…ting around long enough for a Nakamoto block to process)

…s-network/stacks-blockchain into fix/multi-miner-fixes-jude