-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
CI failures with tornado 6.0a1 #4311
Comments
I opened an issue on pip to request the ability to install betas but not alphas: pypa/pip#6110 |
The first traceback there is a failure importing nbconvert; I've made PR jupyter/nbconvert#937 to fix that. No idea about the "Non-websocket response" at the moment. It's probably sensible to constrain tornado<6 for a while, as I've done in #4310. |
I just ran into this issue, should I install of master or do you guys expect to cut a release soon? |
tornado 6.0 dropped today and broke our stuff with this issue. Seems this was not resolved prior to release. |
Also appears to be affecting us. |
@takluyver Looks like jupyter just needs to publish to PyPI. #4310 wasn't included in the last publish on December 17, 2018. |
Since it is atm only in Warning: I'm a conda noob and googled this stuff, but it worked for me. I created one
And updated conda base (aka root) environment with it like so:
thx to SO post: Now I need to remember, when this is fixed in conda and to remove this patch again :) |
That why you should never use undefined package version on your production :D |
The solution from @spex66 worked from me as well. Thanks! |
same error here 😭 |
I was not able to run the newest version install with |
I try the solution from @spex66 , but it seems not to work in my machine,
|
Thx @spex66, this solved my issue as well! 🙌 🚀 🥳 |
The first issue is fixed by nbconvert 5.4.1, the second by notebook 5.7.5 |
in my case, I solved it by specifying to conda to install |
@edgarriba it's already fixed. nbconvert 5.4.1 was out with a fix for web.asynchronous a month ago, while notebook 5.7.5 finished up its own tornado 6 compatibility fixes today. If you're using conda:
should work with tornado 6. Otherwise, |
- `scp` no longer allows the `.` path as the source, so we use `$(pwd)` instead. https://superuser.com/questions/1403473/scp-error-unexpected-filename - Newer tornado does not work with older nbconvert, so we're using new nbconvert now. jupyter/notebook#4311
This is a problem with the nbconvert/notebook and tornado packages which was causing the Jupyter server to fail. Updating to the most recent versions should fix this. See below for more details: jupyter/notebook#4311
@lkhphuc Thanks. It saved my day! |
Same issue with tornado 6.0.2. |
Stop ruining and wasting time of others.. |
Just ran into this issue after upgrading 😐 |
I just ran into this issue again, with fresh installs of jupyter with both pip and conda. The conda stacktraces were:
Which was fixed by chowning |
Tornado 6.0a1 was just released, and is being picked up by Travis CI because we use the
--pre
option to install dependencies. This causes a couple of test failures.We could drop the
--pre
flag and continue testing with Tornado 5.x for now. But it's useful to pick up problems when dependencies are in beta or RC.Tracebacks:
The text was updated successfully, but these errors were encountered: