-
Notifications
You must be signed in to change notification settings - Fork 633
orca always requires mapbox token #1314
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
Comments
With R 3.5.1, Plotly 4.8.0 and Orca 1.1.1 it already happens:
|
This change isn't yet on CRAN |
I'm having a similar issue with the orca function. Also in R 3.51 and Plotly 4.8.0, but if I set MAPBOX_TOKEN to some nominal value then the orca function just hangs (even for a simple line plot of with x=1:10, y=1:10). The depreciated export() function gives me an unusual bug. My data is lognormal, and when rendering points from a lognormal distribution the resulting image is missing all of the points below a certain threshold.
|
Have you tried installing from Github? |
I get an error message: |
Can you run this from the command line? $ orca graph '{ "data": [{"y": [1,2,1]}] }' -o fig.png |
Fails with the below output. I primarily use Python 2.7, could that be part of the issue? Edit: the bolded 'init' below should just have the double underscores wrapping it, not sure how to escape the bold face.
|
I'm not sure, this would be a better venue to get help debugging your setup -- https://github.com/plotly/orca/issues Make sure you can run the 'hello world' examples before using |
I have the same issue here. I have submitted an issue for Orca, but got redirected here, apparently it's an R API problem. Everything works fine if the environment variable exists, the token doesn't have to be valid at all. |
Plotly 4.9.0 doesn't have this problem. Install with |
Like the title says the problem is that the
orca()
function always throws an error that a mapbox token has to be assigned even if the given plot does not depend on mapbox.I don't think a reprex is really needed but anyway:
The text was updated successfully, but these errors were encountered: