-
Notifications
You must be signed in to change notification settings - Fork 61
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
Database call error in methode loadCatalogColors #210
Comments
Hi @d4rken, hmmm... a Spool without a color should not be possible. |
Maybe that's also why I'm always seeing this error, despite everything working? |
Viewing the db, there were 5 entries without I used the plugin UI to view each of the spools without I toggled the colors for each spool (select a different color then the original one again) and saved them. The error is gone now. I still see |
- E release-channles - E stale-bot via github-actions - E #79, #87, #99, #119, #157, #176, #202, weight calculation during editing PR #206, thx al lot @TiziG - E #106 switching from travis to github-actions - E #107, #215 database-settings in the log will only be shown, if sql-logging is enabled - E #170 inform user about switching a spool already selected - E #213 sort/filter options in spool selection dialog - E Extrusion-Debugging: Show current extrusion during printing - B #188 touchUI conflict - B #193, #196 sorting/showing of remaining weight - B #205 changed to "browser-native" date/time picker - B #210 loadCatalogColors when color name is blank - B #211 button text changed - B #212 import CSV only if printer in idle-mode - B #216 FilamentManager and SpoolManager used same viewmodel - B #217 when print is paused the extruded filament is assigned to the spool and the counter is reseted
Hi, Thx in advance |
Yep, seems fixed, thanks! This error still shows though: |
@d4rken please attach the current octoprint.log if you still see the database error. |
I don't think it is necessarily related to this bug, closing this in favor of #223. Thanks for the fix! ❤️ |
After update to
1.5.0
Log
The text was updated successfully, but these errors were encountered: