Proof Portal

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-5002GitHub issuePublicFixed

Keybindings menu (Super+K) spins at 100% CPU: Lua mock incompatible with Lua 5.4+ ipairs

Reported by yzzztech · filed Sep 10, 2026Closed upstream on 2026-09-20 by bjarneo via an automated message, as a duplicate of #7025 (R-1816). GitHub close reason: completed.

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

Keybindings menu (Super+K) spins at 100% CPU: Lua mock incompatible with Lua 5.4+ ipairsrevision 1 · captured 2026-10-04 12:10 UTC via poll

Summary

omarchy-menu-keybindings (the Super+K menu) never renders: its Lua bind scan hangs at 100% CPU whenever the Hyprland config iterates a window-derived value with ipairs/pairs.

Root cause

build_lua_bind_cache loads the user's config in a standalone lua interpreter against a mock of the Hyprland API. The mock's noop object is:

local noop
noop = setmetatable({}, {
  __index = function() return noop end,
  __call  = function() return noop end,
})

Lua 5.4 changed ipairs to consult __index (Lua ≤5.3 used raw access). Omarchy now ships Lua 5.5.1, so ipairs(noop) asks for key 1, gets non-nil noop, asks for key 2, gets noop, and so on forever. Any config that iterates a mock value — e.g.

for _, tag in ipairs(hl.get_active_window().tags) do ... end

spins the scan at 100% CPU and the menu never opens. The mock was written for the old raw-access semantics.

Repro

  1. Add a binding whose config walks hl.get_active_window().tags at load time (or use any config that calls a getter and iterates the result).
  2. Run omarchy-menu-keybindings --print (or press Super+K).
  3. Observe a lua process pegging a core and no menu output.

Minimal Lua repro (hangs):

lua -e 'local n=setmetatable({}, {__index=function() return n end}); for _ in ipairs(n) do end'

Proposed fix

Make the mock return nil for numeric keys so iteration terminates, while keeping noop for named keys (so chaining still works):

noop = setmetatable({}, {
  __index = function(_, key)
    if type(key) == "number" then return nil end
    return noop
  end,
  __call = function() return noop end,
})

A PR with this fix plus a regression test accompanies this issue.

Related (broader) issue

The mock returning a truthy table for every undefined access has a second failure mode: default/hypr/qconsole.lua does monitor.scale <= 0 where monitor = hl.get_active_monitor() is the mock, producing attempt to compare table with number and truncating the scan on the current branch. A more thorough mock redesign (e.g. getters returning nil) would address both, but is a larger change.

Environment

  • Omarchy 4.0.3-1
  • Lua 5.5.1
  • Hyprland 0.56.2
View raw text
## Summary

`omarchy-menu-keybindings` (the Super+K menu) never renders: its Lua bind scan hangs at 100% CPU whenever the Hyprland config iterates a window-derived value with `ipairs`/`pairs`.

## Root cause

`build_lua_bind_cache` loads the user's config in a standalone `lua` interpreter against a mock of the Hyprland API. The mock's `noop` object is:

```lua
local noop
noop = setmetatable({}, {
  __index = function() return noop end,
  __call  = function() return noop end,
})
```

Lua 5.4 changed `ipairs` to consult `__index` (Lua ≤5.3 used raw access). Omarchy now ships Lua 5.5.1, so `ipairs(noop)` asks for key `1`, gets non-nil `noop`, asks for key `2`, gets `noop`, and so on forever. Any config that iterates a mock value — e.g.

```lua
for _, tag in ipairs(hl.get_active_window().tags) do ... end
```

spins the scan at 100% CPU and the menu never opens. The mock was written for the old raw-access semantics.

## Repro

1. Add a binding whose config walks `hl.get_active_window().tags` at load time (or use any config that calls a getter and iterates the result).
2. Run `omarchy-menu-keybindings --print` (or press Super+K).
3. Observe a `lua` process pegging a core and no menu output.

Minimal Lua repro (hangs):

```
lua -e 'local n=setmetatable({}, {__index=function() return n end}); for _ in ipairs(n) do end'
```

## Proposed fix

Make the mock return `nil` for numeric keys so iteration terminates, while keeping `noop` for named keys (so chaining still works):

```lua
noop = setmetatable({}, {
  __index = function(_, key)
    if type(key) == "number" then return nil end
    return noop
  end,
  __call = function() return noop end,
})
```

A PR with this fix plus a regression test accompanies this issue.

## Related (broader) issue

The mock returning a truthy table for every undefined access has a second failure mode: `default/hypr/qconsole.lua` does `monitor.scale <= 0` where `monitor = hl.get_active_monitor()` is the mock, producing `attempt to compare table with number` and truncating the scan on the current branch. A more thorough mock redesign (e.g. getters returning `nil`) would address both, but is a larger change.

## Environment

- Omarchy 4.0.3-1
- Lua 5.5.1
- Hyprland 0.56.2

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/12712· confirmed
  • Fixed bypr/11733· confirmed
  • Fixed bypr/12155· confirmed
  • Fixed bypr/7564· 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.