mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 05:35:30 +02:00
[GH-ISSUE #85] [Bug]: Project stats are a little bit off #41
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#41
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 @mathse on GitHub (Jan 14, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/85
Originally assigned to: @maziggy on GitHub.
Bug Description
The stats of a project are computed quite interesting ... and redundant infos
A: shows "Printed Jobs (Failed and Successful) / Target Print Count (optional)"
B: shows "Successful printed Jobs / Target Print Count (optional) * 100"
C: shows "Printed Jobs (Failed and Successful)"
D: show "Printed Successful Jobs / Target Print Count (optional)"
E: shows "Printed Jobs (Failed and Successful)" two times
Expected Behavior
only a proposal
its all based on my initial assumption that "Target Print Count (optional)" represents the total objects the project will include
Steps to Reproduce
Printer Model
P1S
Bambuddy Version
v0.1.6b7
Printer Firmware Version
recent
Installation Method
Docker
Operating System
Linux (Ubuntu/Debian)
Relevant Logs
Screenshots
No response
Additional Context
No response
Checklist
@maziggy commented on GitHub (Jan 14, 2026):
Yeah, the project page needs some work anyway. Will look into this.
BTW: Thanks for testing and reporting issues continously!
@maziggy commented on GitHub (Jan 14, 2026):
Please use branch 0.1.6b8. Does it look better for you?
@MisterBeardy commented on GitHub (Jan 15, 2026):
Checking out this build and for my workflow, the print job I am submitting will have 6-8 items on a build plate and the project is set to 50 items. So every time the print job is finished, it counts up the objects from that job and moves the progress bar. Now, if I have 50 items set to the Target Print Count, the progress bar only counts completed print jobs not the objects that are printed. This would make sense if it was just one object for each job.
@maziggy commented on GitHub (Jan 15, 2026):
Got it! The complete logic is build on number of prints, where print means plate.
I think the easiest would be, to simply add an additional parts counter.
@maziggy commented on GitHub (Jan 16, 2026):
Please use branch 0.1.6b8 and let me know if that's fine for you.
There's a script in scripts/ which can be used to add parts counts to existing arvchives:
source venv/bin/activate
Preview changes
python scripts/update_archive_quantities.py --dry-run
Apply changes
python scripts/update_archive_quantities.py
@MisterBeardy commented on GitHub (Jan 16, 2026):
Just tested out the new project settings and they work and look great. Nice touch adding the number of plates and parts broken apart. I'll test out the script later today.