I read from the config doc pages that the default is With the the same error message occurs as the one in the screenshot above. #proxy_set_header X-Real-IP $remote_addr īut in the nf I see: config]# cat /etc/nginx/conf.d/nf #Proxy all requests to the GIE Proxy application Plotly.io._infrastructure_url: since I see in our nginx setup: config]# cat /etc/nginx/conf.d/nf Please specify the complete path to the Plotly-Orca binary that you downloaded (for instance in the Miniconda folder) with the following command: If you get an error message stating that the orca executable that was found is not valid, this may be because another executable with the same name was found on your system. Note: as of plotly version 4.9, we recommend using kaleido The situation is similar for environments like Nteract and Streamlit: in these environments you will need a version of these projects that bundles a version Plotly.js that supports the features in the version of plotly that you are running. In any case, regularly upgrading your vscode-python extension to the latest version will ensure you have access to the greatest number of recent features. Plotly figures render in VSCode using a Plotly.js version bundled with the vscode-python extension, and unfortunately it's often a little out of date compared to the latest version of the plotly module, so the very latest features may not work until the following release of the vscode-python extension. VSCode Notebook, Nteract and Streamlit Problems ¶ Note that version 4.14.3 of plotly or earlier needed two extensions ( jupyterlab-plotly and plotlywidget) to be installed manually running, and that plotlywidget requires to be installed: To summarize: if you use JupyterLab with multiple python environments, the extensions must be installed in the "server" environment, and the plotly python library must be installed in each "processing" environment that you intend to use. To check if this is the problem, you can look at the active extension list through your browser via the JupyterLab Extension Manager, which will always list the extensions in the "server" environment. If you accidentally installed the extensions (and run the command above) in one of the additional python environments ("processing" environments), then it is possible for the command above to list the correct extensions but for them to not be available in the JupyterLab front-end you have loaded in your browser. If you have installed additional python environments (or kernels) to use with JupyterLab, or if you are using a centrally hosted JupyterLab installation, you need to make sure that the extensions are installed in the python environment used to launch JupyterLab (the "server" environment). $ jupyter labextension install jupyterlab-plotly You can run the following commands in a terminal to fully remove plotly before installing again: It's often worthwhile to uninstall with both methods before following the Getting Started instructions from scratch with one or the other. It's very important that you not have a file named plotly.py in the same directory as the Python script you're running, and this includes not naming the script itself plotly.py, otherwise importing plotly can fail with mysterious error messages.īeyond this, most import problems or AttributeErrors can be traced back to having multiple versions of plotly installed, for example once with conda and once with pip. Read on for details about troubleshooting plotly in these environments. In general you must also have the correct version of the underlying Plotly.js rendering engine installed, and the way to do that depends on the environment in which you are rendering figures: Dash, Jupyter Lab or Classic Notebook, VSCode etc. This documentation (under ) is compatible with plotly version 4.x but not with version 3.x, for which the documentation is available under. In order to follow the examples in this documentation site, you should have the latest version of plotly installed (5.x), as detailed in the Getting Started guide.
0 Comments
Leave a Reply. |