plotly_IMAGE stopped working
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 2.7k
- Forks
- 641
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
I am not sure if the server is undergoing maintenance. Function plotly_IMAGE suddenly stopped working yesterday. It worked for like 6 or 7 graphs and now returns error [502].
BTW, as a side note, I really would like to have easier options to saving static plotly graphs as PNG. I spent so many hours with this, I tried Orca, Kaleido (which requires installing reticulate, miniconda etc), never made these work because of multiple installing problems, like my user has a space character and miniconda won't install. Anyways, multiple bugs in the process, to finally find the plotly_IMAGE function that somehow worked. I really feel like getting static images is an important feature for R, where many users are forced to used latex to report our works later. Let me know if I can help with this in any way.
The error is:
plotly_IMAGE(global_return_graph, format = 'png', out_file = file.path(savep$
# > Request failed [502]. Retrying in 1.6 seconds...
# > Request failed [502]. Retrying in 1.7 seconds...
# > Request failed [502]. Retrying in 3.9 seconds...
# > Request failed [502]. Retrying in 2.8 seconds...
The same code was working before and just stopped.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported plotly_IMAGE call with format='png' and the shown out_file argument, confirming whether the 502 persists. Then inspect the plotly_IMAGE entry point and its request path; done means identifying and fixing the failure or documenting that the external image service is unavailable, with a regression check for static PNG export.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- data-visualization
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100