-
Notifications
You must be signed in to change notification settings - Fork 5
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
The plugin causes an exception due to missing _progress #10
Comments
How frequently do you get this error? Does it always happen, or only sporadically? |
It appears to have only happened once. Therefore, it may be something odd having to do with refreshing the page while the OctoPrint interface is initializing, but that's only a guess. I couldn't reproduce it by manually doing that. The octoprint version is 1.3.12 and the plugin version is 0.2.0 from pip |
I installed the plugin via the plugin manager yesterday. I kind of have the same error
I had no progress bar during the print. At the end it switched to a full progress bar. OctoPrint 1.4.0 |
I made some more prints and I can confirm, that at the beginning of every print I have the same error.
|
@amittel Have you restarted OctoPrint since installing the plugin? The |
The blank settings page is due to a browser caching issue. Clear your browser cache and it should work. This part is handled by OctoPrint itself, so I don't think I can fix it from my side. As for the main issue: the root cause is that the If my theory is correct, the following sequence should cause the error:
The following sequence should not cause an error:
|
Ok. I got it running. |
I've made a small change so that you're prompted to restart OctoPrint after installation: bugfix/restart Can you try it out before I push the update? |
@cesarvandevelde , I did not had the crash before and was just browsing the issues before I was considering installing this plugin. |
Thanks for the heads-up, @gizmocuz! I've pushed out the fix in a new release. Hopefully, that's the end of that. :) |
The text was updated successfully, but these errors were encountered: