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.

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

Fix OidcBuildStep#findSecurityEventObservers() #26295

Merged
merged 1 commit into from
Jun 24, 2022

Conversation

mkouba
Copy link
Contributor

@mkouba mkouba commented Jun 22, 2022

  • this build step should consume RuntimeConfigSetupCompleteBuildItem
    because DefaultTenantConfigResolver injects a runtime config property
  • resolves OIDC - NullPointerException #26236

@mkouba mkouba requested a review from sberyozkin June 22, 2022 14:46
@mkouba
Copy link
Contributor Author

mkouba commented Jun 22, 2022

@beniaminp It would be great if you could test this PR with your app, i.e. clone the repo and run mvn clean install -Dquickly -T 1 and use the version 999-SNAPSHOT in your app.

Copy link
Member

@sberyozkin sberyozkin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks Martin

@sberyozkin
Copy link
Member

sberyozkin commented Jun 22, 2022

Hi Martin @mkouba

I see

caused by: java.lang.IllegalArgumentException: Cannot consume an empty build item, use @Produce(class) on the build step method instead at io.quarkus.deployment.builditem.RuntimeConfigSetupCompleteBuildItem runtimeConfigComplete of public void io.quarkus.oidc.deployment.OidcBuildStep.findSecurityEventObservers(io.quarkus.oidc.runtime.OidcRecorder,io.quarkus.arc.deployment.SynthesisFinishedBuildItem,io.quarkus.deployment.builditem.RuntimeConfigSetupCompleteBuildItem) of class io.quarkus.oidc.deployment.OidcBuildStep

May be the item should still be returned instead of having void ?

@quarkus-bot

This comment has been minimized.

@mkouba
Copy link
Contributor Author

mkouba commented Jun 22, 2022

Hi Martin @mkouba

I see

caused by: java.lang.IllegalArgumentException: Cannot consume an empty build item, use @Produce(class) on the build step method instead at io.quarkus.deployment.builditem.RuntimeConfigSetupCompleteBuildItem runtimeConfigComplete of public void io.quarkus.oidc.deployment.OidcBuildStep.findSecurityEventObservers(io.quarkus.oidc.runtime.OidcRecorder,io.quarkus.arc.deployment.SynthesisFinishedBuildItem,io.quarkus.deployment.builditem.RuntimeConfigSetupCompleteBuildItem) of class io.quarkus.oidc.deployment.OidcBuildStep

May be the item should still be returned instead of having void ?

Not really. @Consume(RuntimeConfigSetupCompleteBuildItem.class) must be used instead of a RuntimeConfigSetupCompleteBuildItem parameter.

Oh and the error message is misleading.

- this build step should consume RuntimeConfigSetupCompleteBuildItem
because DefaultTenantConfigResolver injects a runtime config property
- resolves quarkusio#26236
@sberyozkin
Copy link
Member

Thanks for taking care of it @mkouba :-)

@quarkus-bot

This comment has been minimized.

@mkouba
Copy link
Contributor Author

mkouba commented Jun 23, 2022

Thanks for taking care of it @mkouba :-)

yw :-)

@mkouba mkouba added the triage/waiting-for-ci Ready to merge when CI successfully finishes label Jun 23, 2022
@beniaminp
Copy link

Hey!
Thanks guys, this was really fast. I am starting to do a test now, I will let you know the outcome.

Thanks again!

@quarkus-bot

This comment has been minimized.

@quarkus-bot
Copy link

quarkus-bot bot commented Jun 23, 2022

Failing Jobs - Building b43a7be

Status Name Step Failures Logs Raw logs
✔️ JVM Tests - JDK 11
JVM Tests - JDK 17 Build Failures Logs Raw logs

Failures

⚙️ JVM Tests - JDK 17 #

- Failing: devtools/cli 

📦 devtools/cli

Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M7:test (default-test) on project quarkus-cli: There was a timeout in the fork

@mkouba
Copy link
Contributor Author

mkouba commented Jun 23, 2022

Hm, the timeout in the devtools/cli in JDK 17 is recurring. I can see the following line in the log:

2022-06-23T12:35:03.5482216Z [WARNING] Corrupted channel by directly writing to native stream in forked JVM 1. See FAQ web page and the dump file /home/runner/work/quarkus/quarkus/devtools/cli/target/surefire-reports/2022-06-23T10-48-28_225-jvmRun1.dumpstream

@gsmet @ebullient @aloubyansky does it ring a bell?

@sberyozkin
Copy link
Member

sberyozkin commented Jun 23, 2022

Looks like unrelated

@sberyozkin sberyozkin merged commit 7d6dab7 into quarkusio:main Jun 24, 2022
@quarkus-bot quarkus-bot bot added this to the 2.11 - main milestone Jun 24, 2022
@quarkus-bot quarkus-bot bot removed the triage/waiting-for-ci Ready to merge when CI successfully finishes label Jun 24, 2022
@gsmet gsmet modified the milestones: 2.11 - main, 2.10.1.Final Jun 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

OIDC - NullPointerException
4 participants