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

Upload fixed data to production #152

Closed
FrostyX opened this issue Aug 9, 2024 · 3 comments
Closed

Upload fixed data to production #152

FrostyX opened this issue Aug 9, 2024 · 3 comments
Assignees
Labels
bug Something isn't working release-blocker

Comments

@FrostyX
Copy link
Member

FrostyX commented Aug 9, 2024

The production instance currently has data with broken snippet indexes. When I fixed the data, I did it in a separate git repository but never actually uploaded them back to production because there was no need. Now we need it otherwise the review page will show nonsense.

Screenshot_2024-08-09_12-43-17

We need to fix this before announcing the review feature.

@FrostyX FrostyX added bug Something isn't working release-blocker labels Aug 9, 2024
@github-project-automation github-project-automation bot moved this to Needs triage in CPT Kanban Aug 9, 2024
@TomasTomecek TomasTomecek self-assigned this Aug 16, 2024
@TomasTomecek
Copy link
Collaborator

TomasTomecek commented Aug 16, 2024

I took the data from the git repo Kuba sent me and crafted a new results/ dir in production that contained the fixed data + all other entries from old results. This is how it looks now:

sh-5.2$ ls -1
fixed-results.tar.gz
results
reviews
letsencrypt
results-old-wrong

sh-5.2$ ls -la results/ | wc -l
65

I ran cp -anr to "copy over": if the file already existed (from fixed-data), it was skipped, otherwise it was copied from results/.

@FrostyX can you please verify I did it correctly?

@FrostyX
Copy link
Member Author

FrostyX commented Aug 19, 2024

This looks good, thank you very much @TomasTomecek.

sh-5.2$ ls -la results/ | wc -l
65

In the "fixed repo" there is only 35 directories, so there is quite a lot of new data. Which should be correct because we already have the fix in production but it may be worth taking a look at a few new results.

@TomasTomecek
Copy link
Collaborator

@FrostyX thanks for checking! I am going to close this then.

@praiskup praiskup moved this from In Progress to Done in CPT Kanban Aug 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working release-blocker
Projects
Archived in project
Development

No branches or pull requests

2 participants