They were all very recent, most of my time is spent doing these! I'll leave it a while and hope they come back *cries*. I think it's more having to do the screenshots all over again.
The one I have that's missing the entire code is fairly new as well. Under a couple weeks, I think. Maybe the backup wasn't that recent. What's weird is that everything is still there minus the code. I'll leave it broken for now in case it helps reveal a bug, but let me know if/when it's not necessary.
To Justin Hindman - New, Positive Feedback: I thanked you in a previous post regarding my 2 longer userstyles' CSS being restored. I made a minor change to one of the styles, then undid the change, which caused the style page to prompt me to update the style in Firefox, which I did to test your restoration efforts. YEA! In my case, the restored CSS resulted in a perfectly working userstyle, AFTER the update completed in Firefox. So, for some of us at least, restoration from your backup, of the previously truncated big-file CSS, is now working. Thanks.
Just realized nothing is showing up in searches for me, example ocuk which I've done 3 themes for, not one is there, thought that got fixed, or did I misread it?
I don't understand. Do you mean that you updated the notes, but didn't update the code?
No. Three times I varied the code, and wrote about this in a "Notes". Now, the style has remained the latest version, but the updating date - old ("Oct 4, 2016" should be "Oct 10, 2016"), also missing three records in the notes (last record "v.0.4". no records about "v.0.5... v0.5.1... v0.5.2..."). link: https://userstyles.org/styles/132956 added: I was wrong! "style settings" are preserved, but the "CSS" block old... no placeholders for "darktheme"
Quick update - the main reason for all bugs you've raised is because I used the AWS migration service, which sucks and it's totally my bad... Some of the tables where there was use of longtext got broken, which mostly effected the long styles. I've managed to restore most of the tables and you should see most styles working well again. Search seems to be working well too, which leaves the weekly install counts as the only main remaining issue. I'm still working on that. Other than that, there are still some local problems with I'm dealing with, so I can't yet say all is back to normal yet, but we're definitely getting there.
It would be a big help if you could review your previous bugs and tell me if you're still seeing them. Thanks
Ok so as predicted you did a rollback to try and fix the issue and it kinda worked... But when installing my style, even though the CSS seemed to be correct, when installed it would make a duplicate of the CSS in an apply to everything selector as well as the specific domains I'd set up which seems a rather odd bug.
I've since updated the style again to make sure it works properly and that seems to have fixed it but might want to be a bit careful for now with those rolled back styles.
Also it turns out, from updating the style it yet again has disappeared completely from search results, AND even after installing the style from the site, the next time I go on that page it thinks it's a different version and wants to update instead of saying "style installed" now.
Double-check to be sure that isn't your v.0.4 code. Some (all?) styles were restored from a backup last night. It's possible that the style metadata was restored but not the style code, but I would check.
Checked. "Style Settings (Optional)" - yesterday code (v0.5.2). "CSS" is old (v.0.4) ..no placeholders for "darktheme".
So, i must wait for changes or begin to recover CSS and notes ( maybe tomorrow)?
This seems to be getting more complicated for you to fix for those people with large styles, I have checked all my styles to see whether it has any deleted parts but I don't think its cut anything off since I don't think my styles were large enough for the chop?
My only issue now is that if you do have a back up and plan to do a full scale revert; is that it will help a lot of people who have lost parts of their code. but some people with small styles like me have already started adding new updates to the styles etc, personally it wont be anything to major for me if a revert takes place since I only made small changes.
However for others it might be annoying if they have already started adding a large amount of new things, so if you do plan to do a full restore from back up just announce it and tell everyone beforehand, so they can save their work if they for some odd reason haven't already been doing so.
Everytime I update my style it disappears on search results, is the new server slow with registering or something
Is the style truncation only at the beginning/end of the file or can it be anywhere? Additionally was it confirmed to only affect style larger than 16KB? My Google style (~100KB) was affected, but I haven't seen any reports on my others (the second largest is 12KB).
Well, I still can't upload anything without the server error so I'm going to take the car. Go to mum's. Kill Phil , grab Liz, go to the Winchester, have a nice cold pint, and wait for all of this to blow over. How's that for a slice of fried gold?
OK but one question keeps nagging at me ... why the hell have we not been informed (by email or something) of this enormous problem?
Exactly what I was saying to myself, even more simple why not a banner on each page stating the site is in transition and there is risk that files/styles are corrupt.
Well, I still can't upload anything without the server error so I'm going to take the car. Go to mum's. Kill Phil , grab Liz, go to the Winchester, have a nice cold pint, and wait for all of this to blow over. How's that for a slice of fried gold?
New problem - the Chrome .json files don't always match the Firefox .css files
[118959] [124745] [129961] The regexps are missing from the .json file, making them global styles in Chrome.
On the plus side, none of them seem to be missing code now. In fact, the styles in the top ten that were corrupt on Oct 10 [1] seem undamaged today [screenshot #1].
Is the style truncation only at the beginning/end of the file or can it be anywhere? Additionally was it confirmed to only affect style larger than 16KB?
I've only seen stylesheets missing data at the end. Unconfirmed - Justin isn't sayin', and I can only guess.
To check a style (1) Download the Firefox file, (2) compute its md5 hash, (3) download the checksum file, and (4) compare hashes. Then (5) download the Chrome file and confirm that (6) the code in the last section isn't truncated and that (7) the "domain" / "url" / "url-prefix" / "regexp" values haven't disappeared from any of the sections. These may help: http://onlinemd5.com/ http://codebeautify.org/jsonviewer
New (?) problem #2 Some stylesheets larger than 0x4000 (16,384) bytes are still truncated. For example, 103864's .css file is truncated to 16,523 bytes and doesn't match its checksum, and its .json file has only a smidgen of badly mangled code [screenshot #2].
Justin, can you please check the code against the hashes?
Everytime I update my style it disappears on search results
That's unexpected. Which style, and what did you search for? I thought that the search database wasn't being updated at all, but if so then your style would still be found with words in the Oct 3 description but not with words you've added since then.
... Well, you are right - the old search terms are lost, and new search terms aren't added.
The "originalMd5" value in this style's Chrome file matches the Firefox file (df75db0d1aef277a24f8cf9c5af47002), though GOK why.
Stylish compares the local value of the checksum with the content of the .md5 file to determine whether an update is available. When a style is installed, Chrome uses the value in the .json file as the local value, and Firefox uses the value in the .md5 file. So, if the .md5 file isn't updated when the style is updated, Chrome will always think there is an update available even after you've installed it, and Firefox will never know there is an update.
I wanted to give you guys a quick update - so far I've managed to partially resolve the search issues. I'm aware of a few styles that still can't be found and am working on that. There were 250 broken styles which I fixed (those broken css you've reported), as well as a legacy issues (unrelated to the migration) of styles that couldn't be updated, which I've also fixed.
What I need now is for you guys to run another check on your issues and tell me what's still open. Remember to include a link to the problematic style and tell me how I can reproduce the bug.
Comments
I think it's more having to do the screenshots all over again.
I linked it in an earlier post, but here it is again:
https://userstyles.org/styles/133094/vk-aquatica-dark-redesigned-layout
I thanked you in a previous post regarding my 2 longer userstyles' CSS being restored. I made a minor change to one of the styles, then undid the change, which caused the style page to prompt me to update the style in Firefox, which I did to test your restoration efforts. YEA! In my case, the restored CSS resulted in a perfectly working userstyle, AFTER the update completed in Firefox. So, for some of us at least, restoration from your backup, of the previously truncated big-file CSS, is now working. Thanks.
https://forum.userstyles.org/discussion/31551/screenshots-for-styles-133517-133565
This thread is going to stay on topic. Report issues, and let Justin know when they are resolved. Thank you.
Just realized nothing is showing up in searches for me, example ocuk which I've done 3 themes for, not one is there, thought that got fixed, or did I misread it?
link: https://userstyles.org/styles/132956
added: I was wrong! "style settings" are preserved, but the "CSS" block old... no placeholders for "darktheme"
I've since updated the style again to make sure it works properly and that seems to have fixed it but might want to be a bit careful for now with those rolled back styles.
Also it turns out, from updating the style it yet again has disappeared completely from search results, AND even after installing the style from the site, the next time I go on that page it thinks it's a different version and wants to update instead of saying "style installed" now.
https://userstyles.org/styles/130610/youtube-umbra
The link again in case you need it to check easier
So, i must wait for changes or begin to recover CSS and notes (
maybe tomorrow)?
My only issue now is that if you do have a back up and plan to do a full scale revert; is that it will help a lot of people who have lost parts of their code. but some people with small styles like me have already started adding new updates to the styles etc, personally it wont be anything to major for me if a revert takes place since I only made small changes.
However for others it might be annoying if they have already started adding a large amount of new things, so if you do plan to do a full restore from back up just announce it and tell everyone beforehand, so they can save their work if they for some odd reason haven't already been doing so.
Everytime I update my style it disappears on search results, is the new server slow with registering or something
message:
An internal server error (500) has occurred.
- Flickr Widescreen - ALLinONE TOTAL (No GM) v.33
- Flickr WideScreen - Dark & Grey v.28
- Yahoo New Mail - Simply Dark and Gray v.33
Thanks !
I need to check my others userstyles......
PS:
A new problem appear , i can't see the review to explain this bug on Userstyle i posted on - by example on this Usertyles:
Flickr Widescreen - ALLinONE TOTAL (No GM) v.33
Exactly what I was saying to myself, even more simple why not a banner on each page stating the site is in transition and there is risk that files/styles are corrupt.
At least on the front page !
:bz
shinuru toki ni mo
he wo kokite
[118959] [124745] [129961] The regexps are missing from the .json file, making them global styles in Chrome.
On the plus side, none of them seem to be missing code now. In fact, the styles in the top ten that were corrupt on Oct 10 [1] seem undamaged today [screenshot #1]. I've only seen stylesheets missing data at the end. Unconfirmed - Justin isn't sayin', and I can only guess.
Useful URLs If 000000 is the style ID in the style page URL,
https://userstyles.org/styles/000000.css is the Firefox file,
https://userstyles.org/styles/chrome/000000.json is the Chrome file,
https://update.userstyles.org/000000.md5 is the md5 checksum, which is also the "originalMd5" value in the Chrome file.
To check a style (1) Download the Firefox file, (2) compute its md5 hash, (3) download the checksum file, and (4) compare hashes. Then (5) download the Chrome file and confirm that (6) the code in the last section isn't truncated and that (7) the "domain" / "url" / "url-prefix" / "regexp" values haven't disappeared from any of the sections. These may help:
http://onlinemd5.com/
http://codebeautify.org/jsonviewer
New (?) problem #2 Some stylesheets larger than 0x4000 (16,384) bytes are still truncated. For example, 103864's .css file is truncated to 16,523 bytes and doesn't match its checksum, and its .json file has only a smidgen of badly mangled code [screenshot #2].
Justin, can you please check the code against the hashes? That's unexpected. Which style, and what did you search for? I thought that the search database wasn't being updated at all, but if so then your style would still be found with words in the Oct 3 description but not with words you've added since then.
... Well, you are right - the old search terms are lost, and new search terms aren't added.
For example, the md5 hash of
https://userstyles.org/styles/118959.css is
df75db0d1aef277a24f8cf9c5af47002,but the content of
https://update.userstyles.org/118959.md5 is
a751922ab04c42e523c431b943b5f851.The "originalMd5" value in this style's Chrome file matches the Firefox file (
df75db0d1aef277a24f8cf9c5af47002), though GOK why.Stylish compares the local value of the checksum with the content of the .md5 file to determine whether an update is available. When a style is installed, Chrome uses the value in the .json file as the local value, and Firefox uses the value in the .md5 file. So, if the .md5 file isn't updated when the style is updated, Chrome will always think there is an update available even after you've installed it, and Firefox will never know there is an update.
Speak, Justin, speak!
http://www.inc.com/bruce-condit/7-critical-steps-to-crisis-management.html
What I need now is for you guys to run another check on your issues and tell me what's still open. Remember to include a link to the problematic style and tell me how I can reproduce the bug.