mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 08:25:54 +02:00
[GH-ISSUE #1171] [Bug Report] Print started without confirming Clear Plate #848
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#848
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 30, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/1171
Originally assigned to: @maziggy on GitHub.
Print started without confirming Clear Plate
System Information
Logs (sanitized): bambuddy.log
Submitted via BamBuddy Bug Report
@tom5677 commented on GitHub (Apr 30, 2026):
Dear Bambuddy team,
in general everything is working fine and Bambuddy is really very useful for my project.
here are some details about the issue:
Today in the morning I was realizing, that the next print in the queue was started without confirming "Clear Plate & Start Next" in the Printer tab.
This caused a fail of two prints and possible damages to the printer. It happened with my P1P and one P1S.
After stopping the print (directly on the printer), now the "Clear Plate" message is showing up for the next print. So this looks OK.
Interstingly the other P1S (2_P1S) is showing the "Clear Plate" message and did not start the next print.
What's the reson(s) for this and how can I avoid it in the future?
Thanks,Tom
@maziggy commented on GitHub (Apr 30, 2026):
Please upload a support package -> https://wiki.bambuddy.cool/features/system-info/?h=debug#enable-debug-logging
@tom5677 commented on GitHub (Apr 30, 2026):
bambuddy-support-20260430-175833.zip
@maziggy commented on GitHub (May 1, 2026):
Thanks for the support bundle and the careful description — both were enough to find the root cause precisely.
What happened: when a print ends with status
aborted(which is what gets reported when you stop a print from the printer's own touchscreen) orcancelled(when stopped from the Bambuddy queue UI), Bambuddy's "Clear Plate" gate that's supposed to block the next queued print was not being raised. Only prints that ended ascompletedorfailedraised it. So the queue scheduler saw your P1P/P1S as available and started the next item about two seconds after the abort — exactly what your log shows:Your second P1S behaved correctly because its previous print had ended
completed, which did raise the gate — that asymmetry you noticed is the bug exactly.Fix: the gate now fires for all four terminal statuses (completed / failed / aborted / cancelled), matching the safety
contract you'd reasonably expect.
Sorry about the close call with your printers — this one should never have gotten past the gate that was put in specifically to prevent it.
Available/Fixed in branch dev and available with the next release or daily build. Please let me know if it works for you.
If you find Bambuddy useful, please consider giving it a ⭐ on GitHub — it helps others discover the project!