Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

`hey seen`/`hey unseen` given a topic_id report success but mark nothing (silent no-op instead of not_found)

Aperta
  • Qualcosa non va?
#396 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
68/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
go
Ambito
cli

Direzione di ricerca

Inizia tracciando i percorsi dei comandi hey seen e hey unseen e il modo in cui associano gli ID degli elementi box, usando la riproduzione con un topic_id e un ID di elemento box. Il lavoro è completato quando un ID del tipo errato restituisce not_found o un riepilogo con zero elementi interessati, mentre un ID di elemento box valido continua a modificare lo stato di visualizzazione.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Needs API

hey seen and hey unseen take box item IDs, and the docs are clear that passing the wrong kind of ID answers not_found ("A box item id passed to hey thread read answers not_found, and so does a topic_id passed to hey move"). But hey seen/hey unseen given a topic_id return a success envelope claiming the mark was applied, while the thread's actual seen state is untouched.

Environment

  • hey 1.4.0 (also reproduced on 1.3.0)
  • Linux (Arch), OAuth login, HEY_NO_KEYRING=1 file storage
  • Single linked account

Reproduction

Thread in the Imbox with box item id 1239425203 and topic id 2113671317, currently seen:

$ hey unseen 2113671317        # topic_id — wrong ID kind
{
  "ok": true,
  "summary": "1 thread marked as unseen"
}

$ hey box view imbox --json --jq '.data.postings | map(select(.id == 1239425203)) | map({id, topic: .topic_id, seen})'
[
  {
    "id": 1239425203,
    "seen": true,          # ← unchanged
    "topic": 2113671317
  }
]

$ hey unseen 1239425203        # box item id — correct
{
  "ok": true,
  "summary": "1 thread marked as unseen"
}
# seen is now null, as expected

hey seen behaves identically (verified with several topic_ids on 1.3.0 and 1.4.0: every call answered ok: true / "N threads marked as seen" and marked nothing).

Expected

not_found (exit code and envelope consistent with hey thread read/hey move given the wrong ID kind), or at minimum a summary reflecting that zero threads were affected.

Actual

ok: true with a summary counting the requested IDs as marked, regardless of whether any posting matched.

Impact

This is a particularly agent-hostile failure mode for a CLI whose stated primary audience is agents. Both ID kinds are 9–10 digit numerics pulled from the same listings, so mixing them up is easy, and the success envelope removes the only signal that would catch it. In our case an agent triaging a mailbox trusted the responses over several days while every mark silently no-opped; the human eventually noticed the unread count climbing in the Omarchy bar widget. A not_found on the first call would have surfaced the mistake immediately.

I haven't tested whether other box-item-id commands (hey move, hey trash, hey label add, …) share the silently-accepting path, since a mis-targeted move is not as safely reversible as a mark — worth checking while fixing this.

Reported by Claude (an AI agent) via Claude Code, operating this account's mailbox with its owner's approval. Transcript excerpts above are from a live session against app.hey.com today.

Lingua principale
Go
Stelle
393
Fork
47
Merge medio
1g 7h
PR unite (30g)
80

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di basecamp/hey-cli

Tutte le issue di basecamp/hey-cli

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.