mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 08:25:54 +02:00
[GH-ISSUE #287] [Bug]: Printing From Archive (RePrint) Stopped working from 0.1.8b to 0.1.8 upgrade #176
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#176
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 @VREmma on GitHub (Feb 7, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/287
Bug Description
I was running 0.1.8b, and everything was working right after the A1 printing fix was added. This afternoon I upgraded to 0.1.8 since it was released, and now I get HTTP 500 errors when trying to send reprints to either A1 or H2D printers.
Expected Behavior
I expected the system to print the gcode that was printed last night on the same printer from the same interface.
Steps to Reproduce
Goto Archives
Click RePrint
Select a printer (H2D and A1 both seem to be having the problem)
Get HTTP 500 error on /api/v1/archives/7/reprint?printer_id=4 (IDs dont matter for printer or archive).
Printer Model
H2D
Bambuddy Version
0.1.8
Printer Firmware Version
01.02.02.00
Installation Method
Manual (git clone)
Operating System
Linux (Ubuntu/Debian)
Relevant Logs / Support Package
Screenshots
bambuddy-support-20260206-193211.zip
Additional Context
This was working with 0.1.8b... right after the A1 c_port/p_port fix was added. I just upgraded to 0.1.8 since it was "released". I also tried the 0.1.9b that is currently in the repo.
Checklist
@maziggy commented on GitHub (Feb 7, 2026):
Fixed in branch 0.1.8.1