Skip to content

Conversation

@kderme
Copy link
Contributor

@kderme kderme commented Nov 20, 2024

Description

Even when is consumed was disabled, db-sync would try to find entries to nullify. This became even worse, since when it's disabled, there are no related indexes.

Checklist

  • Commit sequence broadly makes sense
  • Commits have useful messages
  • New tests are added if needed and existing tests are updated
  • Any changes are noted in the changelog
  • Code is formatted with fourmolu on version 0.10.1.0 (which can be run with scripts/fourmolize.sh)
  • Self-reviewed the diff

Migrations

  • The pr causes a breaking change of type a,b or c
  • If there is a breaking change, the pr includes a database migration and/or a fix process for old values, so that upgrade is possible
  • Resyncing and running the migrations provided will result in the same database semantically

If there is a breaking change, especially a big one, please add a justification here. Please elaborate
more what the migration achieves, what it cannot achieve or why a migration is not possible.

@kderme kderme requested a review from a team as a code owner November 20, 2024 09:30
@kderme kderme force-pushed the kderme/fixes-rollback branch from 09535a4 to 8aceaef Compare November 20, 2024 10:29
@kderme kderme merged commit 1c941df into master Nov 21, 2024
13 of 18 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.

4 participants