The scenario is: 1) User updates their photo (user.save() updates the `modified` timestamp) 2) Celeryd is backed up and doesn't get their photo resized yet 3) User reloads the page, thus getting the old photo with the new modified timestamp into the CDN The solution is: Once celery does its thing, have it user.save() again. This affects all offline processing so the solution should be generic or at least wide spread. I don't know the best solution - maybe a TaskSet could be used to make sure the touch happens after the resizing. Celery also supports after_return, which looks like a wrapper TaskSets+Chords. http://ask.github.com/celery/userguide/tasksets.html I'm putting this in 6.0.7 for discussion as once we flip to the CDN this problem is exaggerated by the long flush times.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.