Script to delete inconsistent vizs #3286 #3342
Merged
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
|
Frontend tests were OK 👍 (details) |
|
I could reproduce it by doing |
|
👍 |
rafatower
changed the title
rafatower
pushed a commit
that referenced
this pull request
Apr 23, 2015
…lwheel Script to delete inconsistent vizs #3286
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.
@Kartones Can you please review? what kind of stuff I might be missing when deleting those?
I'm gonna try to reproduce the conditions of the bug. Dropping the table via sql is not enough (as ghost tables resque sanitizes the vizs). I will try it first locally then in staging. Then I'd try with any of the 15-20 users who suffered the delete viz bug, with least traffic to the offending vizs.