New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash caused by odd escaping in response from http://localhost:8888/lab
request
#7024
Comments
Hmmm, this may actually be an issue with |
Does it work with #7016? |
Lemme check |
@jasongrout #7016 does fix the crash, but the escaping of
Working backwards, it looks like the version string is getting escaped 4 separate times. For each quote, on the first escape you'd get:
then:
and so forth. |
This looks rather suspicious. Perhaps it will work well now that we properly escape things? jupyterlab/jupyterlab/extension.py Lines 144 to 150 in 0d6f4e4
|
I just tested my fix in #7016, and (when I modify the notebook version manually), I get something like |
Actually, it looks like client-side code assumes that notebook version is a string, so I changed it back to a string for backwards compatibility, so it can be backported easily to 1.0.x. I think we can put in a separate PR for 1.1 only that changes the page config value to a JSON array, rather than a string encoding of a JSON array. See the todo note in my amended commit f655977. |
So now the page config entry is |
This may be related to #7016, #7023, and other recent changes/discussion about escaping.
After pulling the latest Jlab code from master, I found that I was unable to load the Jlab client. In my browser's console, I see the following error:
This is the relevant bit of
pageconfig.js
:If I debug and inspect
el.textContents
, here's what I see (with a few fields nulled for privacy):Clearly the issue is the parsing/escaping of my version of the
notebook
package. The above string originates from the response to thehttp://localhost:8888/lab
request that is made during Jlab startup.I am using a dev install of
notebook
, and I can get Jlab to run if I replace it with the release version ofnotebook
, which confirms that the odd escaping ofnotebook
is the cause of my problem.The text was updated successfully, but these errors were encountered: