mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Maintenance time zone conversion incorrect #3412
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#3412
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 @keenmouse on GitHub (Jun 14, 2024).
📑 I have found these related issues/pull requests
Related to #3626, but that involves a recurring maintenance window not taking effect. Mine has to do with time zone conversion for a one-shot maintenance window.
🛡️ Security Policy
Description
👟 Reproduction steps
As shown in screenshots.
👀 Expected behavior
Expected the job in the maintenance window list to display either "2024-06-19 04:00 - 2024-06-19 08:00 UTC+00:00" (as entered) or "2024-06-18 22:00 - 2024-06-19 02:00 UTC-06:00 America/Edmonton" (converted to server/display time zone).
😓 Actual Behavior
Presumably, the window will be applied in the incorrect period displayed.
🐻 Uptime-Kuma Version
1.23.11
💻 Operating System and Arch
Debian GNU/Linux 11 (bullseye) x64
🌐 Browser
Firefox Developer 128.0b1 (64-bit)
🖥️ Deployment Environment
📝 Relevant log output
No response