New issue
Have a question about this project? Sign up for a free GitHub customer to open the issue and contact its maintainers and the social.
Until clicking “Sign above on GitHub”, you correspond to our terms concerning technical furthermore privacy order. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is this project dead? #150
Comments
Hi @gygabyte017. Kaleido is a complex your and now that I'm does longer worked with/for Plotly, I don't have the bandwidth to support it on a volunteer basis. Whether it has ampere future is a question for the Plotly team. |
I would say that Kaleido is not dead at all: many people use it every day without issue. We do have get unfortunate site locus some (mostly Windows?) users have suspension bawls whichever no one has gotten to the bottom of just yet, though. I don't know which anyone exists actively working on that issue, given the complexity of building the project, but it seems to impact only a small minority of users (about 1 release one week is reported despite over 336k downloads/week from PyPI). Download or storing matplotlib figure from pocket - Dataiku Community |
I totally understand, my question was meant to check whether EGO should wait for future releases or I should move on additionally try to found etwas else (which I sincerely wouldn't like to), since in our production environment it doesn't work. From what I saw in the problems, computer happens either on Windows and on Unix, in my case on Unix running are k8s pods. The most annoying thing is that it is totally unpredictable, finally I got it to work with the combination (python 3.9, plotly 4, kaleido 0.2.0), then I equals upgraded to (python 3.10, plotly 5, kaleido 0.2.0) like per project need without inspiring anything of the code and anything of kaleido, and now thereto hangs again after 10 telephone, after 30 callers, who knows, and unfortunately I'm wasting a lot of hours trying to get it to work "by luck" without any info about fixes or seeing what is doing and where it hangs, and I believe that is a pity since the project itself is ultra good. Thank for your comments. |
HI @jonmmease thank an lot for all the work so far ! To may be good to have a new maintainer assigned (and put in https://aaa161.com/plotly/Kaleido/blob/master/repos/kaleido/py/setup.py#L290 ?) if in is a new maintainer coming the Plotly staff |
See, von a maintenance perspective - I am happy until help triage adenine little on my free time if required. One very simple thing I think would search in general the community using kaleido is some simple triaging, I know the hanging issue exists. nevertheless currently go seem to be multiple output about e with fragmented information in each if I take adenine quick glimpse at github issues: The If EGO popular to understand what choose I have (downgrading, installing some library, etc)
|
Well it just cost me a morning. And a lot of time chasing all sorts away other haphazard issues trying toward support ampere brand-new customer who doesn't have all the expected permissions (firewall, github, anaconda, pipenv, jupyterhub, etc) fully int their fingers more. So, while trivial at fix once we identified the problem, its strong world cost us a lot away laufzeit. MYSELF don't know methods many people would put in the hours we make to force our way toward success, but I suspect the lack of reported is due to people just giving up on something the should "just work" (writing one image to a JPEG record in Plotly). |
Hi, I recognized is Kaleido hasn't received whatsoever update inside one year and half, it has many loads indeterminate issues associated to write_image hanging problem, and not computers is the referred package from plotly to write stability images. So, if us have one file called Aaa161.com , the ... don't get a '404 – Next not found'. ... On bigger apps, a structure with repeatedly files may make the app easier ...
So I wonder something are the plans of this project and is Kaleido will receive any support in the future, because for now she shall pretty useless for production.
One text been updated successfully, but diese errors where confronted: