Repository navigation
[Bug] Archived temporary huddle remains visible and cannot be deleted #7026
Description
[A temporary private huddle remains visible in the Buzz Desktop sidebar after its 1-hour lifetime.
Channel Settings still shows “Archive channel” and “Delete channel”, but every action returns:
relay returned 400 Bad Request: invalid: channel is archived
Expected:
- The expired huddle disappears automatically, or
- Desktop shows an Unarchive action and Delete works afterward.
Actual:
- The channel looks active in Desktop.
- The relay considers it archived.
- Archive, Delete, Leave, and member changes all fail.
Channel ID: 1b6049d7…98e8
Platform: macOS
Buzz Desktop version: [invullen via Settings/About]
!IMPORTANT]
Do not include security vulnerabilities in a public issue. Report them
privately through a GitHub security advisory.
Describe the bug
A clear and concise description of what the bug is.
Steps to reproduce
- Go to '...'
- Click on '...'
- See error
Expected behavior
What did you expect to happen?
Version and platform
Find your version at the bottom of the Settings sidebar. Write "unknown" if you can't determine it.
- Buzz version:
- OS:
Logs / additional context
Paste any relevant logs, error messages, or screenshots here.
Activity
noobyogi0010 commentedon Aug 29, 2026
Hey, let me try reproducing this, though do you experience this only when the huddle has been open for an hour?
Thanks!
rlphwlms commentedon Aug 29, 2026
fix(desktop): refresh channels after access-revoked closure (#7784)
fix(desktop): refresh channels after access-revoked closure (block#7784)
rtorcato-bot commentedon Oct 15, 2026
🤖 Automated —
@Optimus Prime🐝 (Buzz agent) via ai-loop.Still happening on Buzz Desktop 0.5.28 (macOS) against a hosted community relay (
*.communities.buzz.xyz).huddle-4d0f89d7was created on Oct 7. Nobody ever posted in it; the only event is "created this channel".buzz channels listorbuzz channels search --query huddle. That fits the relay having archived it while clients still render it from the stale kind39000.This looks like the same root cause as #4879 (the huddle auto-archive never republishes
39000), with the delete path blocked as in #7596 and #2954.GBLab-dev commentedon Oct 29, 2026
Same issue on a hosted community relay (
*.communities.buzz.xyz), Buzz Desktop 0.5.28 on macOS.relay returned 400 Bad Request: invalid: channel is archived. We only ran Delete on one of the four channels; the other three show the same state.archived_atset, but the kind 39000 the client reads has noarchived=true, so the Unarchive → Delete path in Deleting an auto-archived huddle channel returns 400 "channel is archived" #2954 can't be reached from the client.Question for maintainers: on hosted community relays, is there a supported way for the owner to get rid of these today, such as an operator-side republish of 39000 or a server-side delete? Or should we wait for the fix to #4879 / #2954 to be deployed? We'd rather not touch anything by hand. Thanks!