Page MenuHomePhabricator

Corrupted Content Error on Space Discourse
Closed, DeclinedPublic

Assigned To
None
Authored By
Quiddity
Jul 29 2019, 11:20 PM
Referenced Files
F30045624: dd2.PNG
Aug 17 2019, 9:53 PM
F30045625: dd1.PNG
Aug 17 2019, 9:53 PM
F29901600: image.png
Jul 29 2019, 11:20 PM

Description

When I click on a link to Wikimedia Space, I occasionally get an error that looks like this. (Screenshot)
Refreshing the page will usually fix it. Sometimes I have to hard-refresh (ctrl-F5).
E.g. I was logged in and viewing pages normally 20 minutes ago, but I just clicked on a link and got it.

image.png (635×1 px, 45 KB)

Event Timeline

All those recommendations just say "do a hard refresh". Which I already established works! (;P) But then the problem comes back.
(Ok, admittedly they also say "clear your cookies". I'll try that if/when it happens again.)

I get the same error as @Quiddity from time to time. Like they say, a hard refresh fixes it temporarily, but it pops back up again some time later. Deleting cookies doesn't seem to do much for me.

I'm not sure this is related to the same problem, but doing a forced reload (Ctrl + F5) solves it as well, so it might be: From time to time, Space won't display newer posts until I do a forced reload. This has occurred multiple times, even after deleting my browser cookies for both space.wmflabs.org and discuss-space.wmflabs.org

Before forced reload

dd1.PNG (634×689 px, 81 KB)

After forced reload

dd2.PNG (632×703 px, 55 KB)

Qgil triaged this task as Low priority.Aug 22 2019, 10:10 AM
Qgil subscribed.

Low priority only because this seems to be a spotty bug somewhere with a known solution (hard refresh). Let's wait and see whether it keeps happening, also in future versions of Discourse.

Qgil edited projects, added Space (Jul-Sep-2019); removed Space.

I will decline this report, because in practice there is nothing that I see us doing other than wait for more occurrences and (if this is a problem) hoping that this will be fixed upstream.

I this bug comes back, please reopen and we will report it upstream.