404 GET #1702
Labels
needs info
resolved-locked
Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion.
Milestone
Comments
|
There was only an alpha or two where we were looking for something like that path, before we reverted back to |
|
Thanks for the reply. probably some other helpful information is: |
|
Can you examine this in the chrome debugger network pane? There you can see exactly what was requesting the file. It may not be from ipywidgets at all. |
|
Let me know if you need anything more specific. Here is the javascript console output when the notebook loads. Error is in the last 3 lines -- wants me to install There is nothing other than the |
|
What I meant is go into the Chrome debug view, in the Network panel, refresh your page, and look at the Initiator column of that 404 request (or do https://developers.google.com/web/tools/chrome-devtools/network-performance/reference#initiators-dependencies). That will tell you who is requesting that file. Alternatively, perhaps you can go to main.min.js line 36594 like mentioned in the error, and see where that error is coming from. Is it coming from another notebook extension? |
|
In the file Will pull up the notebook in chrome for the other info when I have a little more time tomorrow. |
|
Whoa. This code should have been taken out according to this issue jupyter/notebook#1960 in the notebook. I have |
|
Can you try using the browser incognito mode, to make sure it's not a caching issue? |
|
Found the issue -- Jupyter was reading a notebook.json in the anaconda root dir, rather than user or env dir, which I didn't know about. Not sure why it is doing that though... Hopefully this is solved. Thanks for the help! |
|
Great, I'm glad you found the issue! |
|
Actually didn't stick. So the initiator for the 404 is: Incognito gives the same: |
|
Okay, we expect require to have initiated it. The key is finding out who told require to load it. If what you posted above is still the case (about having that fallback), that seems to be the culprit - outdated javascript of some sort. Now a key is to track down where that javascript is coming from. Can you launch the notebook with |
|
Debug just gives the same as the normal console: |
|
In the server output, underneath the 404, there should be a line like "Path /nbextensions/widgets/notebook/js/extension.js served from ..." That's where it is attempting to serve the extension.js. But even more interesting is: where is it getting that main.min.js that seems to be old? |
|
@jasongrout Its really not giving any more information than I've already provided above. It is using the |
|
When using --debug, the server log should have a line like "Path /path/to/file/main.min.js served from ..."? That will tell you where that old main.min.js file is coming from. That, I think, is the key to knowing why you're loading old code. |
|
Where is the server log? The console? |
|
By server log, I mean the text that is printed out in you terminal after you launch the notebook server, that is, not the JavaScript log or console. |
|
Yeah okay that's what I thought. I've provided that in the initial comment. |
|
Just to confirm, does launching the notebook server with |
|
I continue to see a similar error I tried the proposed solution from that issue Current information: jupyter notebook --debugconda info~/.jupyter cat jupyter_notebook_config.jsonjupyter nbextension listJavaScript console output |
|
I have similar problems... reinstalled my anaconda fro scratch installed everything anew but still with the same problem |
|
@nunocalaim - there are several different problems that have slightly different error messages. Exactly what error are you seeing? Can you post exactly what you did to install everything anew? |
The output with |
|
@soamaven - again, I'm not looking for the /nbextensions/widgets line, but the line that looks like "Path notebook/js/main.min.js served from ..." |
|
Sorry, I apologize for not understanding where exactly to be looking.
prints to where? The browser js console? |
|
I had similar problems, I fixed it with the following command: The sys-prefix seemed to fix whatever issue the conda installer is having in getting the nbextension to properly register the Javascript. |
|
(Hopefully we're dealing with the same problem) |
@soamaven - in the notebook server log, the same place you see the |
|
@ahmadia Yes, thanks, I just came here to post a similar solution! For anyone who may come after me. I am not sure if all steps are required, but they helped me narrow down the possible problem sources. Pretty sure only step 7 as above. So, perhaps just moving files to backups is a more appropriate strategy and slowly adding them back to their proper paths, e.g.
Thanks @jasongrout for your pleasantly persistent help! |
github-actions
bot
added
the
resolved-locked
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
404 GET /nbextensions/widgets/notebook/js/extension.js?v=20170904163701This error is driving me crazy! Uninstalled and reinstalled so many times. Definitely not being loaded via any jupyter config files. Are there any ipython config files that might be looking to load it on notebook load?
Also, there is no yaml spec, so the nbextensions_configurator from user-contrib is no help.
Any advice?
The text was updated successfully, but these errors were encountered: