Roman
Roman
Is the plan to switch to the newly introduced ["same block execution"](https://github.com/tendermint/tendermint/blob/master/spec/abci%2B%2B/abci++_basic_concepts_002_draft.md#next-block-execution-vs-same-block-execution) or keep using "next block execution"? Asking to learn - why would we prefer one over the other...
Please consider adding here to track: https://github.com/cosmos/cosmos-sdk/issues/11923
I would like to resurface this issue and ask what is the plan on this? I'm currently having [some rounding issues in Osmosis](https://github.com/osmosis-labs/osmosis/issues/1917). I have identified that the problem is...
Thanks for the issue. This makes sense but it is still useful for testing. As the node is syncing, I might want to have the data to continue ingesting so...
Is this v13 blocking?
NVM, I see that we went with the code duplication approach for safety here: https://github.com/osmosis-labs/osmosis/pull/3424
I believe this is now solved. Closing for now. Thank you @migueldingli1997
Actually, this is not solved. I mistook it for another refactor we did. Keeping open until further investigations
@mattverse seeing that you are assigned here. Any updates on this? I'm still seeing some twap tests having assets misplaced
I suggest the following: - remove `docker-build-debug` in Makefile - rename `docker-build-debug-alpine` Makefile step to `docker-build-debug`