mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 08:25:54 +02:00
[GH-ISSUE #66] [Bug]: System Time vs. Reported Time #28
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#28
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 @MisterBeardy on GitHub (Jan 9, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/66
Originally assigned to: @maziggy on GitHub.
Bug Description
I have bambuddy running as a docker container on a Debian system and the system date and time is set to TZ America/New_York, yet when I upload a model to the archive to then assign to a project and get ready to send to a printer, the upload time is set to UTC. Tried running the same process on a local dev environment on my MacBook with the latest 1.6-final release and getting the same issue.
Expected Behavior
I would assume that the archive time being shown is based on the system time not UTC. Everything else is displaying the correct time, just not the archived prints
Steps to Reproduce
Upload a print to the archive
Check the date and time of the upload, it shows UTC and not the local time of the system
Printer Model
X1 Carbon
Bambuddy Version
0.1.6-Final and 0.1.6b6
Printer Firmware Version
latest
Installation Method
Manual (git clone)
Operating System
macOS
Relevant Logs
Screenshots
Additional Context
Checklist
@maziggy commented on GitHub (Jan 10, 2026):
Thanks, good catch! Fixed in branch 0.1.6-final. Please let me know, if that works for you.
@MisterBeardy commented on GitHub (Jan 10, 2026):
Sweet, another bug squashed. I just tested it with a new docker build and it's working perfectly. Thanks!