Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Resteasy-reactive void endpoint reported as "Run time writers required" #27338

Closed
Plawn opened this issue Aug 17, 2022 · 2 comments · Fixed by #27413
Closed

Resteasy-reactive void endpoint reported as "Run time writers required" #27338

Plawn opened this issue Aug 17, 2022 · 2 comments · Fixed by #27413
Labels
area/dev-ui area/rest kind/bug Something isn't working
Milestone
2.11.3.Final

Comments

@Plawn
Copy link

Plawn commented Aug 17, 2022

Describe the bug

In dev the UI in the reasteasy reactive endpoint scoring part, my "void" 204 controller are shown as "Run time writers required" but the writer can be determined at compile time

Expected behavior

The correct writer is reported in the Dev UI console

Actual behavior

The endpoint is reported "Run time writers required"

How to Reproduce?

  1. Create a 2.11.2.Final Quarkus app
  2. Add the resteasy reactive extension
  3. Create an endpoint returning "void"
  4. Go to the dev UI

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.11.2.Final

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

maven

Additional information

No response
@Plawn Plawn added the kind/bug Something isn't working label Aug 17, 2022
@Plawn Plawn changed the title Resteasy void endpoint reported as "Run time writers required" Resteasy-reactive void endpoint reported as "Run time writers required" Aug 17, 2022
@quarkus-bot
Copy link

quarkus-bot bot commented Aug 22, 2022

/cc @FroMage, @stuartwdouglas

geoand added a commit to geoand/quarkus that referenced this issue Aug 22, 2022
@geoand
Fix misleading DevUI score for void return types
e7e2a68 
Fixes: quarkusio#27338
@geoand geoand mentioned this issue Aug 22, 2022
Merged
@geoand
Copy link
Contributor

geoand commented Aug 22, 2022

Thanks for reporting.

#27413 takes care of the issue.

geoand added a commit that referenced this issue Aug 22, 2022
@geoand
Merge pull request #27413 from geoand/#27338
25ad6fd 
Fix misleading DevUI score for void return types
@quarkus-bot quarkus-bot bot added this to the 2.13 - main milestone Aug 22, 2022
sheilamjones pushed a commit to sheilamjones/quarkus that referenced this issue Aug 22, 2022
@geoand @sheilamjones
Fix misleading DevUI score for void return types
a2a0a78 
Fixes: quarkusio#27338
@gsmet gsmet modified the milestones: 2.13 - main, 2.11.3.Final Aug 23, 2022
gsmet pushed a commit to gsmet/quarkus that referenced this issue Aug 23, 2022
@geoand @gsmet
Fix misleading DevUI score for void return types
13b8170 
Fixes: quarkusio#27338
(cherry picked from commit e7e2a68)
gsmet pushed a commit to gsmet/quarkus that referenced this issue Aug 23, 2022
@geoand @gsmet
Fix misleading DevUI score for void return types
baa5289 
Fixes: quarkusio#27338
(cherry picked from commit e7e2a68)
fercomunello pushed a commit to fercomunello/quarkus that referenced this issue Aug 31, 2022
@geoand @fercomunello
Fix misleading DevUI score for void return types
09780c5 
Fixes: quarkusio#27338
@StianHaSu StianHaSu mentioned this issue Jul 26, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/dev-ui area/rest kind/bug Something isn't working
Projects
None yet
Milestone
2.11.3.Final
Development

Successfully merging a pull request may close this issue.

Fix misleading DevUI score for void return types geoand/quarkus
3 participants
@gsmet @geoand @Plawn