Skip to content
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(store/streaming): reset BlockMetadata between blocks #18104

Merged
merged 3 commits into from
Oct 16, 2023

Conversation

kocubinski
Copy link
Member

@kocubinski kocubinski commented Oct 12, 2023

Description

Without this fix block meta data files emitted by the file state streaming grow forever since each successive file contains the txs of all prior blocks. This just resets the tx list between blocks.


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...

  • included the correct type prefix in the PR title
  • added ! to the type prefix if API or client breaking change
  • targeted the correct branch (see PR Targeting)
  • provided a link to the relevant issue or specification
  • followed the guidelines for building modules
  • included the necessary unit and integration tests
  • added a changelog entry to CHANGELOG.md
  • included comments for documenting Go code
  • updated the relevant documentation or specification
  • reviewed "Files changed" and left comments if necessary
  • run make lint and make test
  • confirmed all CI checks have passed

Reviewers 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...

  • confirmed the correct type prefix in the PR title
  • confirmed ! in the type prefix if API or client breaking change
  • confirmed all author checklist items have been addressed
  • reviewed state machine logic
  • reviewed API design and naming
  • reviewed documentation is accurate
  • reviewed tests and test coverage
  • manually tested (if applicable)

@julienrbrt
Copy link
Member

Why is this targeting v0.45 given that this version is not maintained and will never be tagged again 🤔

@tac0turtle
Copy link
Member

we should point main and then backport to 047+

@kocubinski
Copy link
Member Author

Why is this targeting v0.45 given that this version is not maintained and will never be tagged again 🤔

I targeted 0.45 because gaia is using a (maintained by them?) branch of 0.45.

we should point main and then backport to 047+

I did not target main because the file changed (store/streaming/file/service.go) was deleted prior, I think in 0.47 not sure top of head.

gaia v13 is released with this cosmos-sdk tag right now https://github.com/cosmos/cosmos-sdk/tree/v0.45.16-ics-lsm

I'd like to get this into whatever conception of "trunk" they're using, I assumed it was this branch, but maybe not. How do you think we should proceed?

@julienrbrt
Copy link
Member

julienrbrt commented Oct 12, 2023

I'd like to get this into whatever conception of "trunk" they're using, I assumed it was this branch, but maybe not. How do you think we should proceed?

They use another branch (https://github.com/cosmos/cosmos-sdk/tree/feature/v0.45.x-ics-lsm), but their SDK version does not deviate from the deprecated v0.45 sdk except for ics and lsm.
This will be another deviation.

We should only maintain supported releases (v0.46 and v0.47) and let this bug be in v0.45 as it isn't a security bug.

@tac0turtle tac0turtle changed the base branch from release/v0.45.x to feature/v0.45.x-ics-lsm October 13, 2023 09:46
@tac0turtle tac0turtle merged commit 4f89b57 into feature/v0.45.x-ics-lsm Oct 16, 2023
24 of 31 checks passed
@tac0turtle tac0turtle deleted the kocubinski/v0.45.x-streaming branch October 16, 2023 09:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants