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(bundles): fix range start block and bundle id when assigning events #69

Merged
merged 1 commit into from
Oct 16, 2024

Conversation

melisaguevara
Copy link
Contributor

This PR fixes two issues related to bundles:

  • When saving the bundle range, we were not incrementing the start block so the end block of each bundle was being repeated as the start block of the next bundle.
  • When relating events to bundles, we were assuming that the bundle id was equal to the id of the proposal, but that might not be true in some cases.

@james-a-morris
Copy link
Contributor

OOC which cases would the ids not match? These are foreign keys to incremental ids

@@ -18,6 +20,9 @@ export class RootBundleCanceled {
@Column()
requestTime: Date;

@OneToOne(() => Bundle, (bundle) => bundle.cancelation)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We would need this to be nullable. I thought we didn't want to change these raw event entities?

Comment on lines -53 to +56
"drb.id",
"drb.blockNumber",
"drb.logIndex",
"drb.transactionIndex",
"crb.id",
"crb.blockNumber",
"crb.logIndex",
"crb.transactionIndex",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fair call but is out of scope

@melisaguevara melisaguevara merged commit 38f81a2 into master Oct 16, 2024
3 checks passed
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.

2 participants