Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.

Inbox
ReportR-2GitHub issuePublicFixed

Clock panel calendar repeats a day and shifts the month after a midnight DST transition

Reported by Andreslvc · filed Sep 28, 2026Closed upstream on 2026-10-07 by its own reporter Andreslvc. GitHub close reason: completed. Closed by its own reporter — not by itself evidence of a fix.

Open at source
Received and recorded verbatim. Nothing has been checked yet.

At a glance

1 · What is claimed?
Only the report text below — no validator has restated it as checkable claims yet.
2 · What does it affect?
Not yet mapped to any requirement or component.
3 · Is it reproducible?
No validation has been run yet.
4 · What remains unclear?
  • Not validated yet: no claims, no reproducer.
5 · What happens next?
Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.

Original report

Clock panel calendar repeats a day and shifts the month after a midnight DST transitionrevision 1 · captured 2026-09-28 21:23 UTC via poll

What happens

In the clock panel calendar, the month containing a DST transition that happens at local midnight shows one day twice, and every later day in the grid is shifted one weekday.

With TZ=America/Santiago (Chile), September 2026 renders week 36 as 31 1 2 3 4 5 5. From then on every date sits under the wrong weekday: Monday 28 appears under TUE.

Expected

Sat 5, Sun 6, and each day under its real weekday.

Cause

shell/plugins/panels/clock/Model.js, monthGrid() (line ~226) starts the cursor at local midnight and steps it with cursor.setDate(cursor.getDate() + 1). Chile springs forward at 00:00 on 2026-09-06, so that midnight doesn't exist; QML's JS engine resolves it backwards to 23:00 on the 5th. The cursor stays on the 5th and the rest of the grid drifts by one.

Fix

Anchor the cursor at noon, so no DST transition can move it across a day boundary:

-  var cursor = new Date(year, month, 1 - leading)
+  var cursor = new Date(year, month, 1 - leading, 12)

Applied locally and verified: the September 2026 grid now shows each day once, under its correct weekday.

System

  • omarchy 4.0.4-1
  • Time zone: Chile/Continental (America/Santiago)

Filed by Claude Opus 5.5 via Claude Code.

View raw text
## What happens
In the clock panel calendar, the month containing a DST transition that happens at local midnight shows one day twice, and every later day in the grid is shifted one weekday.

With `TZ=America/Santiago` (Chile), September 2026 renders week 36 as `31 1 2 3 4 5 5`. From then on every date sits under the wrong weekday: Monday 28 appears under TUE.

## Expected
Sat 5, Sun 6, and each day under its real weekday.

## Cause
`shell/plugins/panels/clock/Model.js`, `monthGrid()` (line ~226) starts the cursor at local midnight and steps it with `cursor.setDate(cursor.getDate() + 1)`. Chile springs forward at 00:00 on 2026-09-06, so that midnight doesn't exist; QML's JS engine resolves it backwards to 23:00 on the 5th. The cursor stays on the 5th and the rest of the grid drifts by one.

## Fix
Anchor the cursor at noon, so no DST transition can move it across a day boundary:

```diff
-  var cursor = new Date(year, month, 1 - leading)
+  var cursor = new Date(year, month, 1 - leading, 12)
```

Applied locally and verified: the September 2026 grid now shows each day once, under its correct weekday.

## System
- omarchy 4.0.4-1
- Time zone: Chile/Continental (America/Santiago)

Filed by Claude Opus 5.5 via Claude Code.

Validation

Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.

Linked

  • Fixed bypr/12943· confirmed
  • Fixed bypr/10476· confirmed
  • Fixed bypr/13186· confirmed
  • Fixed bypr/13751· confirmed
  • Fixed bypr/13096· confirmed
  • Fixed bypr/13127· confirmed

Decision

Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.

No decision has been recorded yet.