This repository was archived by the owner on May 21, 2025. It is now read-only.
Repository navigation
This repository was archived by the owner on May 21, 2025. It is now read-only.
fiber adapter broken since v0.14.0 release #175
Description
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
Reacted by Nacer Laradji, Marvin Wichmann, Fabio Augusto Pereira, Theo Ribeiro, Hugo Azevedo, Emre Sırmalı, Vincent Batoufflet, Tobias Gustafsson and Michael Freeman
Activity
[-]fiber has been broken since v0.14.0 release[/-][+]fiber adapter broken since v0.14.0 release[/+]acidjazz commentedon Apr 27, 2023
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 logsacidjazz commentedon Apr 27, 2023
Issue might be similar to #162
acidjazz commentedon May 9, 2023
@sapessi @bhavik1st can we at least roll these changes back so that a
go get -udoesnt bring down each environment for each project i havetheoribeiro commentedon May 16, 2023
We're having the same issue with the adapter. It would be great if we could roll back these changes. @sapessi @bhavik1st
marvin-w commentedon May 27, 2023
#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.1Feel free to do the same.
marvin-w commentedon Jun 2, 2023
@sapessi Any chance we can merge and publish this soon?
marvin-w commentedon Jun 15, 2023
@sapessi Any update?...
minuchi commentedon Aug 15, 2023
I have also the same problem. Is there any update? 😭
mfreeman451 commentedon Aug 30, 2023
Lets get this fixed
acidjazz commentedon Sep 3, 2023
For anyone interested v0.2.0 of the fume fiber adapter no longer requires this library
0angelic0 commentedon Sep 22, 2023
v0.15.0 was released but it didn't fix this issue.....
acidjazz commentedon Sep 22, 2023
@sapessi we noticed you released an update - can you please address this pretty serious
6 MONTH OLDissuemfreeman451 commentedon Sep 23, 2023
I see this issue has been closed, do we have a workaround now?
marvin-w commentedon Sep 23, 2023
It's part of v0.16.0