Closed gsmet closed 3 years ago
@gsmet yes, it does include additional fixes. What we use HttpHeaders is just to inject it into a method of resource class to be able to access http headers.
@POST()
@Produces(MediaType.APPLICATION_JSON)
@Consumes(MediaType.APPLICATION_JSON)
public TimersModel createResource_timers(@Context HttpHeaders httpHeaders, TimersModel resource) {
In addition I actually tested all this in native and jvm mode and didn't run into any issue, does this fail in native mode only?
Yes the quickstart fails in native mode. Reproduced on quickstart CI and locally.
@gsmet what graalvm version do you use?
It's failing with GraalVM 19.3 on master and was failing with 19.2.1 on 1.1 until I reverted the upgrade.
But I think your usage is legit so we probably need to authorize creating proxies there. I'll see if it fixes the issue.
On Mon, Dec 16, 2019 at 10:54 AM Maciej Swiderski notifications@github.com wrote:
@gsmet https://github.com/gsmet what graalvm version do you use?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/quarkusio/quarkus/issues/6176?email_source=notifications&email_token=AAJYOBJCFNSSRXUCAOC2QDDQY5F6XA5CNFSM4J22YKTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEG6EQ6A#issuecomment-565987448, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJYOBOHXD2IYOBPW7TM5K3QY5F6XANCNFSM4J22YKTA .
ok, let me know if I should investigate anything on Kogito end.
@mswiderski I pinged you on Zulip, let's have the discussion there.
@mswiderski I'm trying to ping you on Zulip. We need a fix quickly so I would appreciate if we could have a discussion. It's probably an easy fix but I need some information from you.
With current master, we have the Kogito quickstart failing with:
AFAICS, it's related to the Kogito 0.6.1 upgrade because we didn't have this issue before.
That being said, it looks like standard RESTEasy code so I'm not sure if it's a bug in Kogito or in the Quarkus RESTEasy extension (missing declaring some potential proxy creation).
@mswiderski did you include something else than the config fix in 0.6.1? It looks like so because if I revert this upgrade, everything is OK. @asoldano does it ring a bell?