Open phillip-kruger opened 2 days ago
:waning_crescent_moon: This workflow status is outdated as a new workflow run has been triggered.
Quarkus CI
This is the status report for running Quarkus CI
on commit 8c038b15c320601c1ef929adefe01f40de803af5.
Status | Name | Step | Failures | Logs | Raw logs | Build scan |
---|---|---|---|---|---|---|
✖ | JVM Tests - JDK 17 | Build |
Failures | Logs | Raw logs | :mag: |
✖ | JVM Tests - JDK 21 | Build |
Failures | Logs | Raw logs | :mag: |
Full information is available in the Build summary check run. You can consult the Develocity build scans.
- Failing: extensions/oidc/deployment
! Skipped: extensions/keycloak-authorization/deployment extensions/oidc-client-filter/deployment extensions/oidc-client-graphql/deployment and 21 more
✖ io.quarkus.oidc.test.CodeFlowDevModeDefaultTenantTestCase.testAccessAndRefreshTokenInjectionDevMode
- History - More details - Source on GitHub
✖ io.quarkus.oidc.test.CodeFlowDevModeTestCase.testAccessAndRefreshTokenInjectionDevMode
line 102
- History - More details - Source on GitHub
✖ io.quarkus.oidc.test.CodeFlowDevModeTestCase.testAccessTokenVerified
line 147
- History - More details - Source on GitHub
✖ io.quarkus.oidc.test.CodeFlowManagementInterfaceDevModeTest.testAuthenticatedHttpPermission
- History - More details - Source on GitHub
✖ io.quarkus.oidc.test.CustomIdentityProviderTestCase.testCustomIdentityProviderFailure
- History - More details - Source on GitHub
✖ io.quarkus.oidc.test.CustomIdentityProviderTestCase.testCustomIdentityProviderSuccess
- History - More details - Source on GitHub
✖ io.quarkus.oidc.test.ImplicitBasicAuthAndBearerAuthCombinationTest.testBasicEnabledAsSelectedWithAnnotation
- History - More details - Source on GitHub
✖ io.quarkus.oidc.test.ImplicitBasicAuthAndCodeFlowAuthCombinationTest.testBasicEnabledAsSelectedWithHttpPerm
- History - More details - Source on GitHub
- Failing: extensions/oidc/deployment
! Skipped: extensions/keycloak-authorization/deployment extensions/oidc-client-filter/deployment extensions/oidc-client-graphql/deployment and 21 more
✖ io.quarkus.oidc.test.CodeFlowDevModeDefaultTenantTestCase.testAccessAndRefreshTokenInjectionDevMode
- History - More details - Source on GitHub
✖ io.quarkus.oidc.test.CodeFlowDevModeTestCase.testAccessAndRefreshTokenInjectionDevMode
line 102
- History - More details - Source on GitHub
✖ io.quarkus.oidc.test.CodeFlowDevModeTestCase.testAccessTokenVerified
line 147
- History - More details - Source on GitHub
✖ io.quarkus.oidc.test.CodeFlowManagementInterfaceDevModeTest.testAuthenticatedHttpPermission
- History - More details - Source on GitHub
✖ io.quarkus.oidc.test.CustomIdentityProviderTestCase.testCustomIdentityProviderFailure
- History - More details - Source on GitHub
✖ io.quarkus.oidc.test.CustomIdentityProviderTestCase.testCustomIdentityProviderSuccess
- History - More details - Source on GitHub
✖ io.quarkus.oidc.test.ImplicitBasicAuthAndBearerAuthCombinationTest.testBasicEnabledAsSelectedWithAnnotation
- History - More details - Source on GitHub
✖ io.quarkus.oidc.test.ImplicitBasicAuthAndCodeFlowAuthCombinationTest.testBasicEnabledAsSelectedWithHttpPerm
- History - More details - Source on GitHub
Quarkus CI
This is the status report for running Quarkus CI
on commit 0d98259214c8c874447e160f945dc955e5c8de74.
:white_check_mark: The latest workflow run for the pull request has completed successfully.
It should be safe to merge provided you have a look at the other checks in the summary.
You can consult the Develocity build scans.
✖ io.quarkus.it.keycloak.CodeFlowTest.testTokenRefresh
- History
expected: <true> but was: <false>
- org.opentest4j.AssertionFailedError
On another note, we can probably use build time data (that can also accept a runtime value) for some of the json-rpc methods. However this is a bigger and riskier change (with the same result) so I kept it simple. If the maintainers (@sberyozkin) wants to pursue this I can show what I suggest.
I am interested.
Thanks @phillip-kruger @michalvavrik, I'll quickly try this PR with both Keycloak and non Keycloak provider, soon and merge then
On another note, we can probably use build time data (that can also accept a runtime value) for some of the json-rpc methods. However this is a bigger and riskier change (with the same result) so I kept it simple. If the maintainers (@sberyozkin) wants to pursue this I can show what I suggest.
I am interested.
@michalvavrik - So for the getProperties
method, that can move to a BuildTimeAction
. This means that you do not need to create a JsonRPC method, you just provide the code in the deployment module. See https://quarkus.io/guides/dev-ui#jsonrpc-against-the-deployment-classpath
The BuildTimeAction
can also take a RuntimeValue that will be returned, meaning you can record the data in the recoreder, and that will be returned on the getProperties call.
This is for #44181. It does not fix it, but takes Dev UI out of the picture.
This PR change the way we make data available to the JSON RPC service. It now use a recorder to record it directly on the JsonRPC Service.
On another note, we can probably use build time data (that can also accept a runtime value) for some of the json-rpc methods. However this is a bigger and riskier change (with the same result) so I kept it simple. If the maintainers (@sberyozkin) wants to pursue this I can show what I suggest.