-
Notifications
You must be signed in to change notification settings - Fork 217
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
Use and combine chain data with LSQ data for stake pools #1769
Conversation
5c84984
to
ffe1b45
Compare
57dbaf0
to
f4cf074
Compare
ffe1b45
to
e8e1d83
Compare
1d36de6
to
24c0b70
Compare
2b6ea47
to
d0386e5
Compare
d0386e5
to
930a3b3
Compare
930a3b3
to
a52ed79
Compare
dbddbb8
to
f076ad3
Compare
f076ad3
to
a6bcca7
Compare
9f102c7
to
bf962fb
Compare
a6bcca7
to
af8d6f3
Compare
2a37581
to
a58a193
Compare
4abf479
to
da24894
Compare
lib/core-integration/src/Test/Integration/Scenario/API/Shelley/StakePools.hs
Show resolved
Hide resolved
a58a193
to
c18da60
Compare
7c94f4f
to
afb32af
Compare
tryBuild failed |
a866694
to
c74ffb7
Compare
bors try |
tryBuild failed
|
bors try |
tryBuild failed |
eventually "Listing stake pools shows expected information" $ do | ||
r <- request @[ApiStakePool] ctx | ||
(Link.listStakePools arbitraryStake) Default Empty | ||
let fixTypeInference = True `shouldBe` True |
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.
You just need a @IO
down below on request
@@ -6,7 +6,7 @@ protocolParams: | |||
protocolVersion: | |||
minor: 0 | |||
major: 0 | |||
decentralisationParam: 0.97 # means 3% decentralised | |||
decentralisationParam: 0.1 # means 90% decentralised |
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.
This was very high to avoid too frequent rollbacks until we have a proper transaction scheduler. I don't think you'll get anything merged with 90% decentralization :)
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.
We can try, but I am afraid this is going to block many PRs after that :/
If their pool registration hasn't been found yet the fields will be left out from the response.
We already have the workers to pool registration certificates and metadata in the data in the DB. Here we read it. - Ignore blocks produced by BFT nodes - Relocate functions and add documentation - Use strategy `chainButNoLsq = dropMissing` - Check that pools produce blocks - fixup: combineDBAndLsqData -> combineDbAndLsqData - fixup: rewrite fetching of certMap
We need to keep this one quite high at the moment in order to prevent the cluster from rolling back too often. The wallet can handle rollback quite nicely, but the integration scenarios cannot (most of them). A lot of scenarios are built following a basic fixture -> action -> assertions principle, and rolling back the fixture can have very negative effects on the rest. We could run every scenario multiple times (at least twice) to maybe cope with intermediate failures due to rollback...
c74ffb7
to
e543f19
Compare
… scenario So that we don't mix concerns between scenarios and we can lower down a bit the assertions without loosing much of the testing benefits.
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.
reviewed, tweaked a few things 👍
bors r+ |
Build succeeded |
Issue Number
ADP-311, #1719
Overview
MsgFetchedNodePoolLsqData
tracereadPoolMetadata
Comments
readMetadata
returns what we previously put in the DB.