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

hey compose to [email protected] publishes the post but reports 406 Not Acceptable (retries create duplicate posts)

Abierto
#556 0 comentarios 1 reacción 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
42/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go
Área
api, cli

Línea de trabajo

The payload names no source files. Start by reproducing with hey compose --to [email protected] -v and checking the redirect handling in the Go HTTP client code that sends the compose POST. Decide whether the 302 should count as success or the redirect should not be followed for this send, since the maintainer has not chosen. Done means a successful POST is reported as sent with ok: true, and a test covers the 302-then-406 sequence.

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

Descripción

Summary

hey compose to [email protected] (HEY World) publishes the post, but the CLI reports a failure:

{ "ok": false, "error": "API error: 406 Not Acceptable", "code": "api" }

Because the command says it failed, rerunning it publishes the post again. Three runs produced three identical public posts.

Steps to reproduce

hey compose --to [email protected] --subject "Test post" < body.md

Verbose output (-v)

http request method=POST
http response status=302
http request method=GET
http response status=406

The POST succeeds and redirects (302). The CLI follows the redirect with a GET that HEY answers with 406, and then reports the whole send as failed.

Expected

  • Treat the 302 after the POST as success (or do not follow the redirect for this send), and report the post as sent/published.
  • At minimum, do not report ok: false when the message was actually accepted, since scripts and agents will retry it and create duplicates.

Related: an idempotency key for compose (#477) would also prevent duplicate posts.

hey version 1.8.0

Lenguaje dominante
Go
Estrellas
409
Forks
49
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.