aws / aws/aws-lambda-runtime-interface-emulator

curl: (52) Empty reply from server

Abierto
#42 2 comentarios 2 reacciones 0 asignados Ver en GitHub
bug
Lenguaje dominante
Go
Estrellas
1.1k
Forks
118
Merge medio
42 min
PR fusionados (30 d)
2

Descripción

I recently ran into an issue trying to test a Lambda function locally with the provided base images. My handler is written in Go. Testing with both `public.ecr.aws/lambda/go:1` and `public.ecr.aws/lambda/provided:al2` gives the same error when attempting to curl the handler locally.

Here are the directions I was attempting to follow to test my function locally. https://gallery.ecr.aws/lambda/go (the Usage tab)

I ended up here after finding this workaround: https://github.com/aws/aws-lambda-runtime-interface-emulator/issues/26. It's my understanding that these steps shouldn't be needed when working with one of the provided Docker images. If there is a better repository to file this issue please let me know. Thanks.

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

Start with the Lambda Go gallery's Usage instructions and reproduce the curl request against public.ecr.aws/lambda/go:1 and public.ecr.aws/lambda/provided:al2. Compare the behavior with the workaround in aws/aws-lambda-runtime-interface-emulator#26; done means identifying why the local handler returns an empty reply and documenting or correcting the affected image or instructions.

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

Evaluación

Stack tecnológico
docker, go
Área
backend, cloud
Tipo de issue
Error
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Estancado
Claridad
Bastante claro
Aptitud para principiantes
35/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.