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

IPython not working when Lightning server is remote #13

Open
bbirand opened this issue Feb 24, 2015 · 1 comment
Open

IPython not working when Lightning server is remote #13

bbirand opened this issue Feb 24, 2015 · 1 comment

Comments

@bbirand
Copy link

bbirand commented Feb 24, 2015

Thanks for working on Lightning, it looks like a phenomenal piece of software. I am having some trouble getting it to work though.

I set up the lightning server on a Heroku instance. I then want to interact with it via IPython, running locally. I wrote the following code, following the examples:

import os
from lightning import Lightning

from numpy import random, asarray, arange

host = 'https://xxxxx.herokuapp.com/'
auth = ('', '')
lgn = Lightning(ipython=True, host=host, auth=auth)
lgn.set_host(host)

lgn.create_session('line-ipython');

y = random.rand(100)
lgn.line(y)

When I run it, a bar appears on the left side of the IPython notebook. But nothing works, and the top logo cannot be displayed. The source of the logo is /images/lightning.svg , although I think it should be https://xxxxx.herokuapp.com/images/lightning.svg. The path for the CSS and the JS files do look correct.

Regardless, all I see is the string 500 instead of the plot.

Any ideas what's happening?

@freeman-lab
Copy link
Member

@bbirand Thanks for reporting this! I'm fairly certain the problem is specific to the heroku build, but there's definitely an issue! I just tried creating a fresh heroku install from scratch myself and found the same behavior you describe.

I did confirm that your example works fine in iPython when running against a local server, or a remote server I created on heroku just a couple weeks ago, so I suspect we pushed something to the server code very recently that's causing this bug (or something changed in the default deployment config).

I'm going to create an issue over on https://github.com/lightning-viz/lightning to track this and loop in @mathisonian .

Thanks again!

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

No branches or pull requests

2 participants