AWS lambda native from documentation doesn't work properly

[Aleksandr-Filichkin]

Describe the bug

The problem is that the first invocation doesn't work, but the second is good.

Expected behavior

No exception in log for the first invocation.

Actual behavior

The problem is that the first invocation doesn't work, but the second is good.
The first invocation

The second invocation

How to Reproduce?

Hi,

I created a simple test project using https://quarkus.io/guides/amazon-lambda and maven
mvn archetype:generate \ -DarchetypeGroupId=io.quarkus \ -DarchetypeArtifactId=quarkus-amazon-lambda-archetype \ -DarchetypeVersion=2.3.0.Final
All code is here
https://github.com/Aleksandr-Filichkin/quarkus-lambda-issue

I deployed the lambda as native using sam deploy -t sam.native --guided.

Output of uname -a or ver

No response

Output of java -version

No response

GraalVM version (if different from Java)

No response

Quarkus version or git rev

2.3.0.Final

Build tool (ie. output of mvnw --version or gradlew --version)

mvn

Additional information

No response

[quarkus-bot]

/cc @matejvasek, @patriot1burke

[Aleksandr-Filichkin]

I built the native file using Docker:

quarkus.native.container-build=true
quarkus.native.container-runtime=docker

[Aleksandr-Filichkin]

I switched to the previous version "2.2.3.Final" and everything works fine.

[Aleksandr-Filichkin]

Also, I think it makes sense to fix maven archetype and do not add the test which cannot be compiled. Or maybe I missed something.
As for me, the hello-world example should work without any manual changes.
https://github.com/Aleksandr-Filichkin/quarkus-lambda-issue/blob/master/src/test/java/test/LambdaHandlerTest.java

[geoand]

@patriot1burke people are reporting the same thing on Zulip as well

[geoand]

@stuartwdouglas I wonder if 363a042 affected this somehow

[patriot1burke]

Ok, I'll fix this stuff. Probably the live coding stuff broke things.

[geoand]

Great, thanks

[patriot1burke]

I can reproduce this from a real lambda deployment, but not in a local test environment. The poll loop is polling a successful request, but it has an empty body from lambda server.

[patriot1burke]

fix incoming