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

curl: (52) Empty reply from server

Ouverte
#42 2 commentaires 2 réactions 0 personnes assignées Voir sur GitHub
bug
Langage dominant
Go
Étoiles
1.1k
Forks
118
Merge moyen
42 min
PR mergées (30 j)
2

Description

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.

Guide de contribution

Ouvrir le guide de contribution

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
docker, go
Domaine
backend, cloud
Type d'issue
Bug
Difficulté
4/5
Temps estimé
3-5 jours
Activité
À l'abandon
Clarté
Plutôt claire
Accessibilité débutants
35/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.