Reduce impact of page topic move that will fail on subpages



3 years ago
3 years ago


(Reporter: jwhitlock, Unassigned)


(Blocks: 1 bug, {in-triage})


(Whiteboard: [specification][type:feature])



3 years ago
What problem would this feature solve?
When moving an MDN topic page (one that has a tree of child changes under it), the move will fail if a "leaf" node will collide with an existing page. 

Who has this problem?
Core contributors to MDN

How do you know that the users identified above have this problem?
While dealing with bug 1279908, several page moves failed.  One attempt was to move:




but there were some existing pages that blocked the move, starting at:


The page move failed. The algorithm is a recursive one that moves pages starting at the top of the topic tree and working it's way down, inside a transaction. When a collision is found, the transaction is rolled back. However, there are a set of page re-renders scheduled for the in-transaction pages, which result in a cascade of async task errors.

How are the users identified above solving this problem now?
1) Attempt a page move
2) Get an email that the page move failed. Forward the email to developers or open a bug
3) Developers get traceback messages, New Relic alerts, etc., and file an incident report.
4) Manual steps are taken to handle the collision and attempt the page move again.

Do you have any suggestions for solving the problem? Please explain in detail.
The page move could be done in "dry" mode, where it attempts to discover collisions before opening the transaction and moving pages.  The page move requester could be notified of collisions before the page move begins.

Is there anything else we should know?


3 years ago
Blocks: 971681
Keywords: in-triage
You need to log in before you can comment on or make changes to this bug.