-
Notifications
You must be signed in to change notification settings - Fork 4
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
consensus roothash events specialization #588
Conversation
ac1d2b2
to
431280b
Compare
c57f3bc
to
3e9b08d
Compare
e0a9684
to
66c1cb2
Compare
cutting this off here, moving messages to a new PR |
the fact that there are no regression test breakages 💀 |
66c1cb2
to
b9b32be
Compare
That's unexpected IMO. The PR modifies the |
b9b32be
to
7f8dd09
Compare
3e9b08d
to
2d6dca4
Compare
7f8dd09
to
d92613b
Compare
2d6dca4
to
3ad6d32
Compare
d92613b
to
a3ab37b
Compare
84ebeff
to
eeacb93
Compare
38f1457
to
2b0f121
Compare
bb67732
to
20a246b
Compare
Co-authored-by: mitjat <[email protected]>
cross-reference: oasisprotocol/oasis-core#5431 Adding this as nilable so we can detect versions below 23.0.3 leaving it out.
660762c
to
8e79657
Compare
3be6019
to
6d1807d
Compare
ok lots of unexplained cache changes, gotta figure this out |
more discussion on the new field names: change them all to roothash_, no more related_. because there's no desire to generalize this to other event types |
ok conclusions on other damask e2e cache changes:
|
6d1807d
to
a9a5ed8
Compare
ok test caches should be set. next is the renames |
roothash events with related runtime and related runtime round