quarkusio / quarkus

Quarkus: Supersonic Subatomic Java.
https://quarkus.io
Apache License 2.0
13.63k stars 2.64k forks source link

Dev UI does not work with Lambda 2.6.2.Final #23014

Open AndLvovSky opened 2 years ago

AndLvovSky commented 2 years ago

Describe the bug

Still seeing issues with Dev UI, described in https://github.com/quarkusio/quarkus/issues/21346#issuecomment-965746375. After opening /q/dev and clicking on any card (for example Config Editor) the UI hangs. Also, no application logs are shown.

Expected behavior

Open Dev UI -> Click on Config Editor -> Be able to view and edit configuration

Actual behavior

Open Dev UI -> Click on Config Editor -> Web page hangs

How to Reproduce?

Steps to reproduce:

  1. Use dependency io.quarkus:quarkus-amazon-lambda-rest:2.6.2.Final
  2. Open Dev UI
  3. Click on Config Editor

Output of uname -a or ver

No response

Output of java -version

openjdk version "11.0.9.1" 2020-11-04

GraalVM version (if different from Java)

No response

Quarkus version or git rev

No response

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

Gradle 6.5.1

Additional information

The issue is not reproducing with Quarkus 2.0.0.Final

quarkus-bot[bot] commented 2 years ago

/cc @matejvasek, @patriot1burke

klutzer commented 2 years ago

@patriot1burke You can find more details on previous (unsolved yet) issue: https://github.com/quarkusio/quarkus/issues/21346 (I would open a new issue but I've found this one with the same problem)

Tested now with 2.6.3 and the problem still remains. Also, after you open Dev UI, your application will not respond even with external calls (or cURLs). This problem only occur when some of the lambda dependencies is added.

This happens on 2.3.0+ versions

klutzer commented 2 years ago

@patriot1burke @gsmet @geoand do you guys have any updates on that?

JohnnMartins commented 2 years ago

I was facing the same problem and solved it change quarkus-amazon-lambda-rest putting it on the profile native.

<profiles>
    <profile>
      <id>native</id>
      <activation>
        <property>
          <name>native</name>
        </property>
      </activation>
      <dependencies>
        <dependency>
          <groupId>io.quarkus</groupId>
          <artifactId>quarkus-amazon-lambda-rest</artifactId>
        </dependency>
      </dependencies>
      <properties>
        <quarkus.package.type>native</quarkus.package.type>
      </properties>
    </profile>
  </profiles>

with that, the error stopped on dev mode.

AndLvovSky commented 2 years ago

I've used the following workaround for Gradle - basically, the dependency is excluded in dev mode:

if (project.gradle.startParameter.taskNames[0] != 'quarkusDev') {
    implementation 'io.quarkus:quarkus-amazon-lambda-rest'
}
geoand commented 1 week ago

Does this still occur with the latest versions of Quarkus?

AndLvovSky commented 1 week ago

I've checked with Quarkus 3.8.6 and when io.quarkus:quarkus-amazon-lambda-rest dependency is present it still hangs

geoand commented 1 week ago

Thanks.

Could you also check with 3.14.4?

AndLvovSky commented 1 week ago

Version 3.14.4 has this problem too

geoand commented 1 week ago

Thanks again!