mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 05:35:30 +02:00
[GH-ISSUE #1113] [Bug Report] Multi-Plate prints using an H2D Pro seems "wonky" We have 3 H2D's but a muti pla #796
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
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#796
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 24, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/1113
Originally assigned to: @maziggy on GitHub.
Multi-Plate prints using an H2D Pro seems "wonky" We have 3 H2D's but a muti plate print is saying we have 4 jobs printing in a 3-printer queue. It seems to be getting confused on what is actually printing.
System Information
Logs (sanitized): bambuddy.log
Submitted via BamBuddy Bug Report
@maziggy commented on GitHub (Apr 24, 2026):
Screenshot please.
@maziggy commented on GitHub (Apr 24, 2026):
Wait...there's something wrong with your network conection to the printer, or the printer was powered off.
2026-04-24 10:00:35,370 ERROR [asyncio] Exception in callback _ProactorBasePipeTransport._call_connection_lost()
handle: <Handle _ProactorBasePipeTransport._call_connection_lost()>
Traceback (most recent call last):
File "C:\Users[USER]\AppData\Local\Programs\Python\Python314\Lib\asyncio\events.py", line 94, in _run
self._context.run(self._callback, *self._args)
~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users[USER]\AppData\Local\Programs\Python\Python314\Lib\asyncio\proactor_events.py", line 165, in _call_connection_lost
self._sock.shutdown(socket.SHUT_RDWR)
~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^
ConnectionResetError: [WinError 10054] An existing connection was forcibly closed by the remote host
@cadtoolbox commented on GitHub (Apr 27, 2026):
This is on repeat in my logs. Ever see this before?
Running Bambuddy on a Windows 11 machine.
@maziggy commented on GitHub (Apr 27, 2026):
Whew....lemme check.
@maziggy commented on GitHub (Apr 27, 2026):
Good news: nothing was actually broken. This was Windows asyncio's housekeeping noise — every time a printer (especially an offline one), the MQTT broker, or a camera dropped its TCP connection abruptly instead of closing it cleanly, Windows logged this traceback even though the reconnect logic was already handling the disconnect correctly behind the scenes. Telemetry resumed normally, prints kept printing, MQTT came back — but the log kept filling.
This release adds a Windows-only filter that recognizes this specific cleanup pattern and demotes it to DEBUG, so it stays out of the regular log unless you turn debug logging on. Real connection-reset errors from your printers (genuine network problems, app-level bugs) are unaffected and still surface as before.
Linux / macOS users: nothing changes. Different event loop, this codepath never fires there.
Particularly visible on installs with several printers offline at once (cadtoolbox's setup that triggered this had 5 offline X1Es and saw the traceback multiple times per minute). After the fix, the log should be quiet again.
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!
@cadtoolbox commented on GitHub (Apr 27, 2026):
@maziggy If it helps explain, we temp removed some printers not in our "Bambuddy" pilot program roll-out by changing the access code in Bambuddy. Everything needs to be gradual when cubicles are involved. ;)