-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
new devui config assumes certain files present #37743
Comments
/cc @cescoffier (devui), @phillip-kruger (devui), @quarkusio/devtools (jbang) |
Hi @maxandersen - when I try to run the reproducer I get:
|
Set that key in a .env file. If still fails remove the call to answer() and rerun. |
Closing here, please reopen if you get this again . |
@phillip-kruger We always have that error log when quitting the dev mode with Dev UI opened with Quarkus 3.2.x and 3.7. It is described in SolaceLabs/solace-quarkus#46. Shall we re-open this issue? |
Yes, if I know how to reproduce I can have a look |
The https://github.com/SolaceLabs/solace-quarkus/ project builds 2 extensions and has 2 sample projects.
|
Thanks @ozangunalp . However when I run the sample app, the test container can not start :
I am using podman - could be that ? |
@phillip-kruger I think so. We need to remove the ulimit and cpuset instructions from this devservice. |
@ozangunalp - how urgent is this ? Can I wait until the podman issue is solved so that I can look at this, or do I need to install docker to get this reproduced ? |
It is not urgent, but it reliably reproduces this issue. I'll check the dev service provided in this extension to work on podman. Then we can take a look. |
I don't have much hope work making the Solace dev service work on Podman. |
Describe the bug
git clone https://github.com/maxandersen/javaadvent-2023-quarkus-ai-scripting/blob/main/devhelper.java
run
jbang --fresh -Dquarkus.dev -Dquarkus.console.enabled=false devhelper.java
now goto http://localhost:8080/q/dev-ui and try use the configuration view.
It will look like its frozen.
eventually in logs/errors you get:
funny enough the devui config will try turn that exception into a table of values.
Expected behavior
dont fail when running with jbang.
dont treat errors as valid input when rendering config ui.
Actual behavior
No response
How to Reproduce?
No response
Output of
uname -a
orver
No response
Output of
java -version
No response
Quarkus version or git rev
No response
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: