-
Notifications
You must be signed in to change notification settings - Fork 1
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
Cannot terminate the process #27
Comments
@B3J4y I run the test on windows at it works smooth. Just a question: did the figures open on your browser or not? If not it might be a problem with some close ports that do not allow plotly to open the figures and, therefore, not ending the process. Let us know! |
@B3J4y Thank you! Therefore, there might be some issue with the saving of some of the output files. When you run it, is it saving some output files in the output directory or not? If yes, what output files is ProMCDA saving? |
Perfect, thanks! I know this is quite a tough way to try to fix an issue. In any case, it looks like that the issue is related to the figures, probably in the saving of them in the output folder. I'll have a look at it. I'll keep you posted |
@B3J4y I guess I found the issue. It looks like that it is related to kaleido, which is used to save the static image of the plotly plots. In some cases (only on windows and not for everyone) the new version of kaleido (0.2.1), which is used in ProMCDA, is not correctly working. To solve this the community propose to downgrade kaleido to the version 0.1.0.post1 as discussed in https://community.plotly.com/t/static-image-export-hangs-using-kaleido/61519 and plotly/Kaleido#126 |
@mspada Thank you for finding the solution. I haven't had the time to downgrade Kaleido, and I feel that whether it works or not, your package will be very weak in terms of reusability if it relies on this mechanism for your Windows users. Could you possibly package it into a Docker container and add a Dockerfile to the repository? This could solve the Windows problems and provide users with a system-independent way to run the software. |
After running the toy example, the process did not finish, and I was unable to terminate it properly.
The text was updated successfully, but these errors were encountered: