Page MenuHomePhabricator

Uncaught Error: Unknown dependency: site
Closed, ResolvedPublic


I get the following when I visit Commons (user_talk history) and reload a page on my mobile.

Running Chrome 53

Screenshot_20161009-170014.png (2×1 px, 259 KB)

To replicate:

If you delete the page the error disappears

Event Timeline

Lokal_Profil renamed this task from Unkaught Error: Unknown dependency site to Unkaught Error: Unknown dependency: site.Oct 9 2016, 4:11 PM
Reedy renamed this task from Unkaught Error: Unknown dependency: site to Uncaught Error: Unknown dependency: site.Oct 9 2016, 4:36 PM
Reedy added a project: Mobile.

site is not available on mobile. I'm not sure why this is being marked as dependency of something. It sounds like a gadget is depending on this. @Krinkle any ideas what might be happening here?

ovasileva moved this task from Incoming to Needs Prioritization on the Web-Team-Backlog board.

@bmansurov can you reproduce now with the steps i've added?

@bmansurov to be clear - you saw it happening when following the steps in the description on a local instance?
Note I cannot replicate it on as I don't have your gadget so it's a little confusing sharing that link.

I was not able to reproduce it locally. I don't think I have gadgets either on commons.

By gadget I mean this (mine is empty which is why I cannot replicate). What do you see when you test locally with the above steps? Is it possible you don't have $wgAllowUserJs = true; set locally?

After adding $wgAllowUserJs = true; I see the error locally too.

I can reproduce this in production, on I only have a common.js page on my user account, no minerva.js and it still causes the error.

Screen Shot 2016-10-11 at 21.17.00.png (1×2 px, 652 KB)

This is caused by the mobile site now loading the "user" module (it used to have its own version of the user module). This module has a hardcoded internal dependency on the "site" module since its execution must happen after the site module finished loading. This is a legacy requirement that has always been the case with user scripts since they cannot explicitly express this dependency anywhere else.

Before 2015, when our script loading was still synchronous, this was implicitly done by one being after the other in the HTML as separate script tags. Now that loading happens asynchronously, this is ensured by ResourceLoader. This has been the case since at least August of last year.

Since MobileFrontend has a custom user and site module without the 'common.js' portion, the only remaining script is minerva.js which has presumably has had an expectation from very early on that it does not depend on the site-wide Minerva.js script.

I'm not sure why this is being marked as dependency of something. It sounds like a gadget is depending on this.

It's not being loaded by a gadget. It's loaded directly from the HTML output:

Krinkle added a project: Regression.
Krinkle moved this task from Inbox, needs triage to Radar on the Performance-Team board.
Krinkle added a subscriber: Regression.
Krinkle removed a subscriber: Regression.

@bmansurov @ovasileva Any more analysis needed or can we schedule this work (move to triaged but future)?

I do't see this problem any longer. was it solved ?

Jdlrobson claimed this task.

Yup. Looks fixed to me (although minerva js is run twice still - that's captured in another bug).

The error message in the console went away after rMW7e2e2db806f6: mw.loader: For using() errors, reject Promise instead of throwing. The site module is still not available on mobile (and shouldn't be, per MobileFrontend design). And as before, the user module will continue to execute unaffected after ResourceLoader fails to load the implicit site dependency.