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

event add fails with --link; succeeds without it (HTTP 403 observed)

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

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
18/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
go
Ambito
cli

Direzione di ricerca

Start with the --link flag in internal/cmd/events.go, then check how it maps to calendar_event[url] in go/pkg/hey/calendar_events.go in hey-sdk. Reproduce with a public HTTPS URL to see whether the 403 depends on the link value, and compare the request with a no-link run. Done means the link is accepted or the CLI returns a clear validation error, with the cause recorded.

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

Descrizione

A timed event with --link failed through the CLI, while the same reference URL was saved successfully through HEY's normal browser event form.

Observed results
  • In a cloud Linux environment, HEY CLI 1.7.0 (SDK 0.31.1, OAuth) returns Form request failed (HTTP 403) from POST /calendar/events.json.
  • On my own machine, the command also fails with --link and succeeds when only that argument is removed. The local CLI version and exact local error have not yet been captured for this report.
  • The same event and URL were successfully saved through the signed-in browser interface. CLI readback preserved the URL.
  • OAuth status, inbox reads and calendar reads work.

The reference is a private HTTPS HEY email-thread URL, omitted here. No public-URL reproducer has been verified, so this report does not establish that every --link value fails.

The argument was supplied as --link '<private HTTPS reference URL>' alongside the normal title, calendar, date, time-zone, location and notes options. The pinned CLI documents --link as "Meeting or reference URL" and passes Content.Link to calendar_event[url]. Current source uses the same mapping.

A diagnostics-only build preserving the request, authentication and transport found an HTML 403 body containing CAPTCHA/browser-challenge-related keywords. The provider and root cause are unknown; no raw body, credentials or headers are included here.

Expected

The CLI should accept the reference URL that HEY's browser form accepts, or return an actionable validation error.

Could you investigate the link-dependent failure and advise on a supported fix?

References
Lingua principale
Go
Stelle
412
Fork
52
Merge medio
22h 16m
PR unite (30g)
75

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.