-
Notifications
You must be signed in to change notification settings - Fork 6
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
error 500 #72
Comments
I'll look into this, I think for the time being you can resolve it by going to settings and deleting the human toxicity method and trying again - the method names have changed in the latest version of brightway which runs the calculations. This is likely the same problem as #69 Let me know if that doesn't work |
The latest version of
For some reason the default install is still 0.4.2 which still has the bugs, might be something to do with github tags, I'll look into it |
No ignore that - that makes things worse - some other bug has come up in the meantime with eidl/bw2data - don't update yet |
It worked now. Apparently Firefox doesn’t work with the program.
Google Chrome works though.
Thanks anyway!
Von: James Joyce<mailto:[email protected]>
Gesendet: Donnerstag, 2. April 2020 11:44
An: pjamesjoyce/lcopt<mailto:[email protected]>
Cc: Nora Korp<mailto:[email protected]>; Author<mailto:[email protected]>
Betreff: Re: [pjamesjoyce/lcopt] error 500 (#72)
No ignore that - that makes things worse - some other bug has come up in the meantime with bw2io - don't update yet
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#72 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/APA7LPKPAXRTVNLRMKHIIITRKRM6FANCNFSM4L2EVPWQ>.
|
Cool, that new error might just be for me then... There's a separate issue with pickle version 5 and backward compatability for python 3.7 |
Hello, how do you delete the human toxicity method as it is not showing any option to delete? |
When analyzing the climate change impact for black tea in my method, error 500 keeps occuring.
The text was updated successfully, but these errors were encountered: