-
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
Fix benchmarks in Buildkite #169
Conversation
So that stack doesn't eat them.
-- Failure response (e.g. 404 /mainnet/tip). | ||
-- This can be recovered from by retrying the request. | ||
Left e@(FailureResponse _) -> | ||
return $ Left $ ErrNetworkUnreachable $ T.pack $ displayException e |
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 shouldn't be in the default handler because the semantic we give to 404
is different depending on the endpoint. Actually, 404 are already handled for epochs for instance. If this is needed for the /networkTip
endpoint, let's add it to the getNetworkTip
handler, like done for getEpoch
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.
OK, moved. I tried both
getNetworkTip :: ExceptT ErrNetworkUnreachable m (Maybe (Hash "BlockHeader", BlockHeader))
-- and
getNetworkTip :: ExceptT ErrNetworkTip m (Hash "BlockHeader", BlockHeader)
The latter seems better.
8236d1e
to
6576e43
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.
LGTM. I wonder however when would the network tip be not available? When the bridge just got started 🤔 ?
Relates to #100
Overview
The builds are here: https://buildkite.com/input-output-hk/cardano-wallet-nightly