add miner diagnostic to block proposal data#6989
add miner diagnostic to block proposal data#6989brice-stacks merged 5 commits intostacks-network:developfrom
Conversation
This doesn't actually add a lot of useful things yet; at this point it's just a skeleton implementation of the approach I'm thinking about.
|
This plan makes sense to me! My main request is to add unit tests with existing block proposal fixtures (ie hex serialized versions) and do simple round-trip serialization tests. That's helped catch footguns in the past with these kinds of things. Edit: I'm sure you've seen this, but for one change I just copy/pasted the old implementation into our tests, as a simple way of testing backwards compatibility. |
I already added some such tests for the |
|
Ah yes I do now see that we already have that kind of test, so you wouldn't be adding new coverage. Great! |
882e272
Codecov Report❌ Patch coverage is
❌ Your project status has failed because the head coverage (84.98%) is below the adjusted base coverage (84.99%). You can increase the head coverage or adjust the Removed Code Behavior. Additional details and impacted files@@ Coverage Diff @@
## develop #6989 +/- ##
===========================================
- Coverage 84.99% 84.98% -0.02%
===========================================
Files 412 412
Lines 219958 220044 +86
Branches 338 338
===========================================
+ Hits 186959 186996 +37
- Misses 32999 33048 +49
... and 40 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
The exact list of things that should be included in the diagnostics data is up for debate -- please opine on what things might be useful.
https://github.com/stx-labs/core-epics/issues/194