Cairn

Discord UI view classes broken by lazy install timing

NousResearch/hermes-agent · cluster 26958 · gateway

Data as of

Nothing open on GitHub. Fix merged in #28817. Check it covers your case.

The short answer

0open issues
0open PRs
6items grouped
Known?
Yes. 6 related items grouped here, 2 issues already closed.
Fix event
A fix was merged to main in PR #28817. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #28817. That is separate from the fix event.
Still open
Nothing open on GitHub.

A bug where Discord View/UI component classes were defined before the lazy discord.py install completed, leaving discord=None at class definition time and causing NameError failures. Multiple fix attempts address defining these classes after the lazy install.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #28817 fix(discord): define UI view classes after lazy install (#26958)

    merged to main

    files: gateway/platforms/discord.py, tests/gateway/test_discord_lazy_install_views.py

3 PRs closed without merging

From the close comments: merged via another change 2 · done elsewhere 1

  • #27019 fix(discord): define View classes after lazy install via _define_discord_views() · merged via another change → 5a33176, #28817, #28261
  • #28261 fix(discord): define view classes after lazy discord.py install · done elsewhere → 5a33176
  • #28729 fix(discord): define UI component views lazily for lazy-install compa… · merged via another change → 5a33176, #28817, #28261, #27019, #28729
Closed issues · 2
  • Closed#26958[Bug]: Discord View classes never defined — lazy-install leaves discord=None at class definition time
  • Closed#28045Discord button-based exec approval fails with NameError: ExecApprovalView is not defined — falls back to /approve text
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.36: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
gateway
Merged PRs
#28817
Closed issues
2
Attempts
3 PRs closed without merging
Fix link checked
19 May 2026

For your agent

The same facts, typed.

cluster/26958.json
cluster/26958.md