Skip to content
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

The latest ipython branch doesn't work in Chrome #934

Closed
certik opened this issue Oct 26, 2011 · 10 comments
Closed

The latest ipython branch doesn't work in Chrome #934

certik opened this issue Oct 26, 2011 · 10 comments

Comments

@certik
Copy link

certik commented Oct 26, 2011

It works great in Firefox. I don't have time currently to debug this, but in Chrome, it doesn't show any cells if I create a new notebook. My ipython master is a3c02d8.

@fperez
Copy link
Member

fperez commented Oct 27, 2011

What version of Chrome and Tornado are you using? Unfortunately, a few days ago in their dev channel, chrome changed their websocket protocol identifier and broke with released tornado. Major PITA for us...

@minrk
Copy link
Member

minrk commented Oct 27, 2011

Yes, and tornado master has been updated to work.

We really need to draw a message on the error (426) that unsupported websockets causes.

@fperez
Copy link
Member

fperez commented Oct 27, 2011

Marking for 0.12 so at least we provide a meaningful error instead of the blank stare of death :)

@certik
Copy link
Author

certik commented Oct 27, 2011

I use the latest tornado, and Chrome 15.0.874.102. Definitely, some useful error message is necessary.

@fperez
Copy link
Member

fperez commented Oct 30, 2011

BTW, this is the tornado commit that fixed the problem for them. I talked to Brian also about this, and I think the most sensible solution for our users is to apply that commit as a tornado monkeypatch for now. I'm going to submit a PR with the monkeypatch just now so that our regular users don't have to fight too much with this for now.

@fperez
Copy link
Member

fperez commented Oct 30, 2011

PR opened at #948 to take care of the tornado part. We'll close this once we also have a proper error message.

@minrk
Copy link
Member

minrk commented Oct 30, 2011

closed by merge of #948

@minrk minrk closed this as completed Oct 30, 2011
@certik
Copy link
Author

certik commented Oct 30, 2011

I confirmed that this fixes it for me. I am closing the issue.

@fperez
Copy link
Member

fperez commented Oct 30, 2011

Nobody actually read my note above, did you ? :)

I deliberately did not close this issue until we also had a proper error message for the lack of websocket connections, though in all fairness that's a slightly different problem. I was just trying to keep things simple by having only open open issue around the whole problem.

Opened #952 then...

@certik
Copy link
Author

certik commented Oct 31, 2011

I was thinking about this, but then concluded that this issue really is fixed, and the warning is a different issue (but I should have opened the new issue for it), and then hit "comment & close", and then I noticed, that Min has already closed it in the meantime.

Thanks for fixing it so fast! Everything works excellent for me again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants