-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Open
Labels
aws:lambdaAWS LambdaAWS Lambdastatus: backlogTriaged but not yet being worked onTriaged but not yet being worked ontype: bugBug reportBug report
Description
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
I have deployed a Golang Lambda that is set up to be a streaming function URL. When hitting the deployed URL my code will complete, but the client will receive the following error instead of the data the URL wrote:
{"__type": "InternalError", "message": "exception while calling lambda with unknown operation: Extra data: line 1 column 222 (char 221)"}
FWIW I have similar code running in production on AWS Lambda so I strongly believe the problem is on Localstack side.
I have a minimal reprod repo for y'all here: https://github.com/sno6/localstack-lambdaurl-issue
Expected Behavior
I expected cURL
to receive the data that the lambda wrote to the response writer. Also, I expect that using the -N flag would result in the response streaming in to the client.
How are you starting LocalStack?
With the localstack
script
Steps To Reproduce
- Clone https://github.com/sno6/localstack-lambdaurl-issue
- Run
make build
- Deploy the stack using cdklocal.
curl
the deployed function url.
Environment
- OS: Mac OSX
- LocalStack:
LocalStack version: LocalStack CLI 4.2.0
Anything else?
No response
Metadata
Metadata
Assignees
Labels
aws:lambdaAWS LambdaAWS Lambdastatus: backlogTriaged but not yet being worked onTriaged but not yet being worked ontype: bugBug reportBug report