You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
We need to fix this before announcing the review feature.
The text was updated successfully, but these errors were encountered:
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?
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.
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.
We need to fix this before announcing the review feature.
The text was updated successfully, but these errors were encountered: