Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#555 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
18/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
go
Área
cli

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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
Lenguaje dominante
Go
Estrellas
412
Forks
52
Merge medio
22 h 16 min
PR fusionados (30 d)
75

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de basecamp/hey-cli

Todos los issues de basecamp/hey-cli

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.