Decide: two overlapping schedule rules of the same priority #54
Labels
No labels
Area/Backend
Area/Database
Area/Docs
Area/Frontend
Area/Infra
Area/Security
Area/Tests
Area/Tooling
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Lang/Python
Lang/Rust
Lang/Shell
Lang/SQL
Lang/TypeScript
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Routing
Auto
Routing
Hold
Routing
Human
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Grimoirix/grimoire-of-digital-signage#54
Loading…
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?
What
Define specificity for 'the more specific rule wins'.
Done when
Rule written into scheduling.md.
Plan
plan/server/scheduling.md (Open)
Routing/Hold: no agent is routed to this issue automatically. To take it yourself, assign yourself. Vivy removes the hold when it is handed to an agent.Created for GRI-1818 from
plan/overview/roadmap.mdand the MVP plan on GRI-1761.The overlap is decided: the more specific rule wins.
When two scheduled rules of the same priority cover the same device and the same
time, the more specific rule wins.
Specificity is how narrow a rule is, and it is measured on the two dimensions
a scheduled rule narrows: the device scope and the time window.
device group, so a device-specific setting beats a group setting.
broader than a date range, which is broader than a single date. Within a
recurring kind, a narrower time range is more specific than a wider one.
A rule is more specific than another overlapping rule when it is narrower on the
device scope, or when the device scopes are the same and it is narrower on the
time window. The more specific rule is in force; the broader rule yields. The
alternative, that the most recently edited rule wins, is rejected.
ANSWER
When two scheduled rules of the same priority overlap on the same device and
the same time, the more specific rule wins.
SUBSTITUTED
no substitution
NAMES AND NUMBERS
device scope ranking = a single device is more specific than a device group [https://git.grimoirix.org/Grimoirix/grimoire-of-digital-signage/src/branch/dev/plan/server/scheduling.md]
time window ranking = a single date is more specific than a date range [https://git.grimoirix.org/Grimoirix/grimoire-of-digital-signage/src/branch/dev/plan/server/scheduling.md]
most recently edited fallback = rejected [https://git.grimoirix.org/Grimoirix/grimoire-of-digital-signage/src/branch/dev/plan/server/scheduling.md]
WORKING
no arithmetic: this is a decision over two candidates, not a measurement
FETCHED
https://git.grimoirix.org/Grimoirix/grimoire-of-digital-signage/src/branch/dev/plan/server/scheduling.md (774 of 774 words)
SEARCH-ONLY
NOT ESTABLISHED
the runtime behaviour of the deployed client under overlapping rules; this
decision fixes the server's rule set, and the client is told which rule won.
Closed: the overlap is decided — the more specific schedule rule wins, with specificity defined on device scope and time window, written into plan/server/scheduling.md and the open question marked decided. Decision comment above.