feat: add timeout info to initChain and finalizeBlock resps#432
Conversation
|
should pull in latest of celestiaorg/celestia-core#1672 and eventually lock in when merged |
rootulp
left a comment
There was a problem hiding this comment.
LGTM. Seems like this PR is:
- propagating TimeoutInfo in a few ABCI responses
- uses replace statements to pick up changes needed for the TimeoutInfo propagating
and I assume the replaces will look cleaner (i.e. use an official release) after we merge some other prerequisite work
|
It looks like the e2e/tx service suite is failing. So will need to look into that. From what I can see grpc/grpc-gateway tx query with txHash is hanging, and we hit a timeout alarm in CI and it also hangs for me locally. Also some failures in the TxEvents (off by one errors in expected len of tx results) for both grpc and grpc-gateway too. Seems comet/celestia-core related I guess. |
|
possibly something to do with Tx query looking to get a shareProof for inclusion and calling into a custom abci request query endpoint which won't exist in the simapp under test in here. |
|
I actually think its deadlock because of that ^^ core will lock on the query conn when calling how was this avoided previously, or am I missing something? |
x/upgrade/go.mod
Outdated
| replace github.com/cosmos/cosmos-sdk => ../../. | ||
| replace ( | ||
| // celestia-core | ||
| github.com/cometbft/cometbft => github.com/celestiaorg/celestia-core v0.38.11-0.20250325150452-89ef6e8a5cb3 // marko/core_changes_v3 |
There was a problem hiding this comment.
random note that all these aws imports reminds me we need to merge celestiaorg/celestia-core#1437
There was a problem hiding this comment.
I was going to ask about them on the core PR actually!
rootulp
left a comment
There was a problem hiding this comment.
@damiannolan do you need us to cut celestia-core and/or cosmos-sdk releases so we can fix the replace directives in this PR?
| // use cosmos fork of keyring | ||
| github.com/99designs/keyring => github.com/cosmos/keyring v1.2.0 | ||
| // celestia-core | ||
| github.com/cometbft/cometbft => github.com/celestiaorg/celestia-core v0.38.11-0.20250331172655-bbd3b9bdd1ee |
There was a problem hiding this comment.
Seems like we should create a celestia-core release so this can use an official release. Is everything merged in celestia-core and you just need a release?
There was a problem hiding this comment.
If you want to cut a rc/alpha tag on core then that would be great. We could pick that up here.
I'm not 100% sure if everything is merged. There was still some discussion around mempool, right?
There was a problem hiding this comment.
I don't have enough context on the v0.38.x branch and what the plan is regarding celestia-core releases moving forward so I don't feel comfortable cutting a release from that branch.
@tac0turtle what's the status of v0.38.x in celestia-core? Is it safe to cut release candidates from?
| github.com/cometbft/cometbft => github.com/celestiaorg/celestia-core v0.38.11-0.20250331172655-bbd3b9bdd1ee | ||
|
|
||
| github.com/cosmos/cosmos-sdk => ../../. |
There was a problem hiding this comment.
[blocking]
These replaces should use official releases
There was a problem hiding this comment.
Agree, but on the release branch I think it is normally using local replace, but when tagged is locked in to an official version. cc. @julienrbrt
There was a problem hiding this comment.
Yes, once you tag the SDK, you should bump x/upgrade go.mod to use that version and tag x/upgrade.
See description from #430
rootulp
left a comment
There was a problem hiding this comment.
Approving to unblock but we need a follow up issue or PR to update the replace directives to use official releases
9d04f7a
into
celestiaorg:release/v0.50.x-celestia
…org#432) * chore: go1.23 everywhere * chore: use go1.23 * feat: add timeout info to initChain and finalizeBlock resps * chore: use latest celestia-core branch * chore: set prove flag to false for query tx * chore: add changelogs * chore: pin to HEAD of v0.38.x-celestia (core) adjust
Description
Depends on #431 to clean diffs.
TimeoutInfotype.TimeoutInfotoEndBlockand propagates inInitChainandFinalizeBlockresponses.Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...
!to the type prefix if API or client breaking changeCHANGELOG.mdReviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...
!in the type prefix if API or client breaking change