890915 - DoesNotExist: current_revision on Web/CSS

Status: RESOLVED FIXED

(developer.mozilla.org Graveyard :: General, defect)

Description

[Luke Crouch [:groovecoder]]

What did you do?
================
1. https://developer.mozilla.org/en-US/docs/Web/CSS

What happened?
==============
ISE

What should have happened?
==========================
no ISE

Is there anything else we should know?
======================================
Caused a bunch of ISE's: https://errormill.mozilla.org/mdn/mdn/group/29691/

The document current_revision was set to 438435, but there's no revision in the database with that id. :/

I updated the current_revision back to the previous revision - 438429; but we need to find out why and how it get set to a non-existent revision?

Comment 2

[Saurabh Nair [:jsx] (not reading bugmail. ni? if you need me)]

Someone edited css landing on  6th/7th which messed up the layout.

Then :trevorh of #devmo tried to revert to an earlier revision, but was getting timeouts.

Later :JoshStrobl of #devmo tried, but failed to do revert. When he tried, it didn'tt actually save the changed source and just ends up saying "no data sent".

Comment 3

[truthfromlies]

Web/CSS is no longer returning a 403 / 404. Please mark this bug as RESOLVED. Thank you.

Comment 4

[Luke Crouch [:groovecoder]]

We should still investigate whether timeouts during revision requests (save, revert, move, etc.) cause erroneous updates to Document.current_revision.

Comment 5

[raymond [:retornam] (inactive)]

I tried this on stage using this page.

https://developer.allizom.org/en-US/docs/tools

I was able to revert to older revisions without a time out or 404 error. The only thing I can think of that I haven't tried yet is to people with admin permissions trying to revert at the same time

Comment 6

[Luke Crouch [:groovecoder]]

Thanks :retornam. Must have been the celery issues failing the revision saves.