-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chain switch trace events: record old and new SelectView
#384
Conversation
7361fd8
to
cd46472
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not Approving only because (as you hinted in your Slack message), I think the field name is maybe a little too confusing.
ouroboros-consensus/src/ouroboros-consensus/Ouroboros/Consensus/Storage/ChainDB/Impl/Types.hs
Outdated
Show resolved
Hide resolved
ouroboros-consensus/src/ouroboros-consensus/Ouroboros/Consensus/Storage/ChainDB/Impl/Types.hs
Show resolved
Hide resolved
cd46472
to
44c503b
Compare
44c503b
to
7458090
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice 👍
@@ -636,7 +649,7 @@ data TraceAddBlockEvent blk = | |||
-- chain (second fragment). | |||
| AddedToCurrentChain | |||
[LedgerEvent blk] | |||
(NewTipInfo blk) | |||
(SelectionChangedInfo blk) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Once this diff context appear it occurred to me that perhaps the dowstream use cases of NewTipInfo/SelectionChangedInfo
could just get the SelectView
from the two header chain arguments.
However, Esgen pointed out the call site would then need to also have the BlockConfig
in scope. (That's certainly always possible, but likely often onerous).
No description provided.