Page MenuHomePhabricator

App sees old content right after edit
Closed, ResolvedPublic1 Estimated Story Points

Description

When RESTBase is enabled it takes a while after an edit for the content to be generated. There is not much left we can do on the RB side.

We could add something to the app code to ensure that after a successful edit the app retries to get a new revision of the page. Until then keep spinning or show a Snackbar.

This is a follow up of T123938.

Event Timeline

@mobrovac @GWicke Would it be possible to send a specific HTTP header to the server that would block the response until the revision of a page changes and generation of the next revision is complete?

@mobrovac @GWicke Would it be possible to send a specific HTTP header to the server that would block the response until the revision of a page changes and generation of the next revision is complete?

Nope, that's not in line with the REST philosophy, unfortunately. The original problem is an artefact of the jobqueue being backlogged. We are now in the process of transferring the processing of updates to the change-propagation service which should minimise the amount of time it takes for the edit to become visible.

MBinder_WMF set the point value for this task to 1.May 18 2016, 7:21 PM

Change 290349 had a related patch set uploaded (by Dbrant):
Add a small artificial delay after saving an edit.

https://gerrit.wikimedia.org/r/290349

Change 290349 merged by jenkins-bot:
Add a small artificial delay after saving an edit.

https://gerrit.wikimedia.org/r/290349

Dbrant claimed this task.