Georgios Andrianakis

icon company @RedHatOfficial icon location Athens, Greece icon location Principal Software Engineer @ RedHat, part of the core Quarkus team

Results 773 comments of Georgios Andrianakis

Context is lost when using caching

Also cc @jponge

Micrometer URI templating does not apply for Forbidden requests

Your sample is **not** using Quarkus REST (formelly known as RESTEasy Reactive). However even with it, https://github.com/quarkusio/quarkus/pull/40308 is required to make the tests pass.

`@UnlessBuildProperty` does not work properly if `io.quarkus:quarkus-rest` in the dependencies.

Thanks for reporting. Is there any chance you narrowed down which version actually introduced the breakage?

`@UnlessBuildProperty` does not work properly if `io.quarkus:quarkus-rest` in the dependencies.

Thanks!

Always populate metrics uri in presence of auth failures

The reason I have not added a test is that surfacing the problem requires a different security setup than the one of the existing integration tests and I am not...

Always populate metrics uri in presence of auth failures

> > The reason I have not added a test is that surfacing the problem requires a different security setup than the one of the existing integration tests and I...

WebSocket + Role-based authentication stopped working with Quarkus 3.9.x: Security Identity is not available

Let me try and summarize so as to check if I have understood the issue correctly: There is some piece of code that runs in a Vertx route that runs...

WebSocket + Role-based authentication stopped working with Quarkus 3.9.x: Security Identity is not available

It's definitely possible to use the existing request scoped state if it exists, but is that really something we want to do in all cases?

WebSocket + Role-based authentication stopped working with Quarkus 3.9.x: Security Identity is not available

> Can you think of a case where that would be an issue? Not off hand

WebSocket + Role-based authentication stopped working with Quarkus 3.9.x: Security Identity is not available

What I think can become problematic is how we handle the end of the request processing in Quarkus REST. Currently as we always start the context, we always terminate it...