mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Push error if Kuma its off #733
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#733
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 @FlorianMifsud on GitHub (Jan 10, 2022).
⚠️ Please verify that this bug has NOT been raised before.
🛡️ Security Policy
Description
If I have a "PUSH" type monitor and I check every minute if I turn off the Kuma server and turn it on again 2 minutes later, it will notify the "push" type monitors in error
👟 Reproduction steps
Create a push notification
Shutdown a server X minutes
Reup a server
👀 Expected behavior
😓 Actual Behavior
🐻 Uptime-Kuma Version
1.11.3
💻 Operating System and Arch
Linux version 5.10.75-79.358.amzn2.x86_64 (mockbuild@ip-10-0-40-76) (gcc10-gcc (GCC) 10.3.1 20210422 (Red Hat 10.3.1-1), GNU ld version 2.35-21.amzn2.0.1) #1 SMP Thu Nov 4 21:08:30 UTC 2021
🌐 Browser
Safari
🐋 Docker Version
No response
🟩 NodeJS Version
v17.3.0
📝 Relevant log output
No response