gsmet.bsky.social
Happy camper at Red Hat. Improving Quarkus one commit at a time.
14 posts
207 followers
91 following
Getting Started
comment in response to
post
Thanks!
comment in response to
post
Thanks to me and a lot of others! That's the plan!
comment in response to
post
I decided try to reproduce it based on the stacktrace we got. I managed to do it and posted the reproducer. One hour later, my colleague created a PR with a fix.
So please, pretty please, provide reproducers, it makes a huge difference and is the best guarantee to get your issues fixed promptly.
comment in response to
post
Also building a simple reproducer quite often give us a better idea of where to look at because you will have to isolate the issue. github.com/quarkusio/qu... is a good example of this. We didn't have a proper way to reproduce it. My colleague decided to close the issue - which is our process. 🧵
comment in response to
post
Note that I'm all for finding a way to escape from this vicious circle and ideally the best way to do it is to contribute fixes that help make this thing more solid.
comment in response to
post
Yeah, unfortunately, it's a bit of a vicious circle. Given it's brittle, we are always afraid to break something and as we don't have experts to review changes, things can be slow. I'll try to have a look at the PR during the holiday.
comment in response to
post
Gradle is a very flexible and complex beast and that makes integration with it a lot more difficult... and unfortunately quite brittle. The fact that we don't have Gradle expertise in house doesn't help. Issues with test cases are welcome (and contributions even more so!).
comment in response to
post
FWIW, we have seen very weird behaviors/bugs with GraalVM for Java 17, we are not recommending it at all. Things are moving so fast, it's hard to provide stable information about the versions you should use...
comment in response to
post
👋