mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 08:25:54 +02:00
[GH-ISSUE #1055] [Bug Report] All filaments have disappeared and when adding new ones they also don't show. #748
Labels
No labels
A1
automated
automated
bug
bug
Closed due to inactivity
contrib
dependencies
dependencies
duplicate
enhancement
feedback
hold
invalid
Notes
P1S
pull-request
security
ThumbsUp
user-report
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/bambuddy-maziggy-1#748
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @maziggy on GitHub (Apr 20, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/1055
Originally assigned to: @maziggy on GitHub.
All filaments have disappeared and when adding new ones they also don't show.
System Information
Logs (sanitized): bambuddy.log
Submitted via BamBuddy Bug Report
@maziggy commented on GitHub (Apr 20, 2026):
This is nothing I can work with. Please explain your issue in detail.
@fdsghy4a commented on GitHub (Apr 20, 2026):
None of my spools are showing on the filaments page, and adding new ones literally doesn't do anything. This has been an issue for a few days now. There were around 20 in there working just fine for a few weeks, and then one day POOF, gone. Adding looks like normal but after saving, there's still nothing.
@maziggy commented on GitHub (Apr 20, 2026):
Did you follow the release notes when upgrading?
@fdsghy4a commented on GitHub (Apr 20, 2026):
As far as I'm aware I have... Also it wasn't right after an update, it was randomly one day last week right after adding a couple of new spools. It was all there and working fine, and then I went back to the filaments page a few minutes later and suddenly nothing.
@maziggy commented on GitHub (Apr 21, 2026):
Again, you need to be more precise.
Also please
@fdsghy4a commented on GitHub (Apr 21, 2026):
Like I said, it wasn't in connection to an update! It was running fine and then suddenly it just wasn't working after adding a couple of new rolls.
Everything is pulled via portainer (re-pull image and redeploy), and I usually have it pull from daily. Updated to the latest version in hopes that it would fix this issue, and sent the bug report in when it did not.
As for the logs, I added a spool/replicated the issue fully (with recording) when submitting the report. So the logs sent with the report is apparently all it logs when adding a spool. But of course, I'll try to find some time later to do that.
@maziggy commented on GitHub (Apr 21, 2026):
Your logs are just a few lines and don't show any useful information.
@fdsghy4a commented on GitHub (Apr 21, 2026):
Well that is unfortunately all it logs when it records while sending in a bug and replicating the issue.
@maziggy commented on GitHub (Apr 21, 2026):
Please upload a support package -> https://wiki.bambuddy.cool/features/system-info/?h=debug#enable-debug-logging
@fdsghy4a commented on GitHub (Apr 21, 2026):
See attached. Also attached a screen recording of the issue.
bambuddy-support-20260421-102704.zip
https://github.com/user-attachments/assets/5f346c5a-c88e-4824-bfb9-afa8f6c8ec54
@maziggy commented on GitHub (Apr 21, 2026):
You don't enabled debug logging. Please follow the instructions I've sent you.
Also please open your browser console, force a page reload (Shift+Reload) and check for any errors in browser console.
@fdsghy4a commented on GitHub (Apr 21, 2026):
Actually, I did enable debug logging and followed the instructions exactly. As you can see in the logs it even says "2026-04-21 10:26:28,540 INFO [backend.app.api.routes.support] Log level changed to DEBUG"
The screen recording is NOT from when debug logging is on, they are separate. I added it after to give you more info.
@maziggy commented on GitHub (Apr 21, 2026):
I don't see any errors on your logs.
You still don't answered my questions.
@fdsghy4a commented on GitHub (Apr 21, 2026):
I actually answered that earlier lol.
I've think I've found the issue, getting this error in the browser consol:
index-DRV_S8BY.js:35 GET http://xxx.xxx.x.xx:8000/api/v1/inventory/spools?include_archived=true 500 (Internal Server Error)
@maziggy commented on GitHub (Apr 21, 2026):
No, you din't answer these questions.
This MUST also generate a backend error log. Need to see that please.
@fdsghy4a commented on GitHub (Apr 21, 2026):
One would think so, but the logs I sent are literally what it logs when in debug following the wiki instructions:
1. Go to System Information page
2. Find Support & Troubleshooting section
3. Click Enable to turn on debug logging
4. A banner appears across all pages showing debug mode is active with a live timer
5. Reproduce the issue you want to report
6. Click Download to get the support bundle
In the support package I sent, after "2026-04-21 10:26:28,540 INFO [backend.app.api.routes.support] Log level changed to DEBUG" I went straight to the filaments page, tried to add a spool, and then went back to the system. information page and clicked download on support bundle. What I've uploaded is that download. 😕
@maziggy commented on GitHub (Apr 21, 2026):
No logs....hmmmm.....
Please do the following:
cd /opt/bambuddy/frontend && npm i && npm run build && sudo systemctl restart bambuddy && tail -f /opt/bambuddy/logs/bambuddy.log | grep -v "error|warning|failed"
Reload page, add spool and check backend and browser logs.
@fdsghy4a commented on GitHub (Apr 21, 2026):
I did some checks in portainer before seeing your latest reply and I found the issue.
fastapi.exceptions.ResponseValidationError: 1 validation error:
{'type': 'string_pattern_mismatch', 'loc': ('response', 1, 'rgba'), 'msg': "String should match pattern '^[0-9A-Fa-f]{8}$'", 'input': 'FFFFFFF', 'ctx': {'pattern': '^[0-9A-Fa-f]{8}$'}}
Somehow, one of my filaments has an RGBA value of FFFFFFF (7 characters), but it's (obviously) expecting 8 characters. How this actually happened I have literally no idea since I always click one of the pre-existing swatches or use the color selector tool. As it is, one somehow saved with 7 characters which made the GET /api/v1/inventory/spools request crash with a 500 error.
I have edited my database to add the missing F which has fixed the issue, spools are now loading as they should!
Something I would hope you can look into is why it's able to save with the incorrect number of characters in the first place, and maybe a fix to block it from being able to do so?
@fdsghy4a commented on GitHub (Apr 21, 2026):
Actually I also want to add this so you know: I just looked at which spool matches the ID of the spool that had the missing F, and it's not one of the spools I added that day: it's one that had been there for a few weeks already (which no changes were made to that day when it all stopped working). I can't tell you if it always had a missing F or not, like I said I've been using the swatches and color picker, but somehow it ended up missing an F in the database at some point in time, and some time last week that missing F made it stop showing all spools.
@maziggy commented on GitHub (Apr 21, 2026):
Thanks for letting me know.
Available/Fixed in branch dev and available with the next release or daily build.
If you find Bambuddy useful, please consider giving it a ⭐ on GitHub — it helps others discover the project!