The comparison of m_best_invalid with the tip of the chainstate makes no sense for the background chainstate and can lead to incorrect log messages.
Fixes #30958
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--006a51241073e994b41acfe9ec718e94-->
For detailed information about the code coverage, see the test coverage report.
<!--021abf342d371248e50ceaed478a90ca-->
See the guideline for information on the review process.
| Type | Reviewers |
|---|---|
| ACK | TheCharlatan, fjahr, tdb3, achow101 |
If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update.
The comparison of m_best_invalid with the tip of the respective chainstate
makes no sense for the background chainstate, and can lead to incorrect
error messages.
ACK c0a0c72b4d68a4f0c53c2c4b95f4d6e399f8e4ee
utACK c0a0c72b4d68a4f0c53c2c4b95f4d6e399f8e4ee
CR ACK c0a0c72b4d68a4f0c53c2c4b95f4d6e399f8e4ee
ACK c0a0c72b4d68a4f0c53c2c4b95f4d6e399f8e4ee
Milestone
28.0