search

awslabs / aws-lambda-go-api-proxy

lambda-go-api-proxy makes it easy to port APIs written with Go frameworks such as Gin (https://gin-gonic.github.io/gin/ ) to AWS Lambda and Amazon API Gateway.
Apache License 2.0
1.03k stars 197 forks source link

fiber adapter broken since v0.14.0 release #175

Closed acidjazz closed 9 months ago

acidjazz commented 1 year ago

Ever since this release any attempt to upgrade results in Internal Server Error on lambda and no logs in cloudwatch. This results in all of my Lambda+Fiber+Go projects going down until I hard-code this back to v0.13.3

acidjazz commented 1 year ago

I have verified this on 3 different projects by switching back and forth from v0.14.0 to v0.13.3, all go back and forth from working fine to crashing with Internal Server Error - only duplicate-able in lambda and no logs

acidjazz commented 1 year ago

Issue might be similar to https://github.com/awslabs/aws-lambda-go-api-proxy/issues/162

acidjazz commented 1 year ago

@sapessi @bhavik1st can we at least roll these changes back so that a go get -u doesnt bring down each environment for each project i have

theoribeiro commented 1 year ago

We're having the same issue with the adapter. It would be great if we could roll back these changes. @sapessi @bhavik1st

marvin-w commented 1 year ago

181 will fix this. Until it is released, I'm using.

replace github.com/awslabs/aws-lambda-go-api-proxy => github.com/marvin-w/aws-lambda-go-api-proxy v0.14.1

Feel free to do the same.

marvin-w commented 1 year ago

@sapessi Any chance we can merge and publish this soon?

marvin-w commented 1 year ago

@sapessi Any update?...

minuchi commented 10 months ago

I have also the same problem. Is there any update? 😭

mfreeman451 commented 10 months ago

Lets get this fixed

acidjazz commented 10 months ago

For anyone interested v0.2.0 of the fume fiber adapter no longer requires this library

0angelic0 commented 9 months ago

v0.15.0 was released but it didn't fix this issue.....

acidjazz commented 9 months ago

@sapessi we noticed you released an update - can you please address this pretty serious 6 MONTH OLD issue

mfreeman451 commented 9 months ago

I see this issue has been closed, do we have a workaround now?

marvin-w commented 9 months ago

It's part of v0.16.0