Fixing gravity table corruption bug when pulling. #48
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks @theobjectivedad. I'm reactivating this project. Would you mind checking to see what's conflicting with your proposed merge? Thanks! |
|
any chance we could see these fixes merged? edited to remove suggestion that theobjectivedad's fork doesn't work in a container environment on the pull side. It seems to work ok. I had not gone through the pihole-cloudsync setup process again. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #32
Root cause: Basically, a hard drop of
adlistanddomainlistcorrupts FKs in$gravity_db. Also, the way CSVs were imported caused data type corruption. This update will correct both issues.