Joe Barnett

for what its worth we've worked around this by using the antrun maven plugin instead of the ktlint maven plugin: https://github.com/trib3/leakycauldron/blob/cabaf522652be90550e4d0f8d7ccde50335116d6/parent-pom/pom.xml#L1472-L1498 -- that way the rest of the build still...

@trautonen Looks like the Kotlin issue is caused by its compiler inlining functions, and the extra lines are the best solution they have: https://youtrack.jetbrains.com/issue/KT-9766 Given this, would you be more...

if it's helpful, we used to attempt to deploy our dropwizard app in lambda using https://github.com/trib3/leakycauldron/blob/v1.27.2822/lambda/src/main/kotlin/com/trib3/lambda/TribeServerless.kt -- cold start times were too slow to be useful so we deprecated &...

it appears that building from the repo creates a dynamically linked binary that works, while the statically linked binary downloaded from the github releases has this issue. not sure why...

not sure what you mean about Force Touch, but certainly possible i messed something up with that last commit. i see the copy working pretty much how I want it...

its my attempt to avoid the "as dev I copy something and select another to delete then paste. But I paste exactly what I deleted" problem -- I usually double...

haha yes, almost stable indeed -- seems like some amount of highlight, pause and move mouse, command+c copy, pause and move mouse, ok go ahead and work normal works most...

I've changed it to "@vue/eslint-config-prettier" in my project and it appears to work

> ~(dropwizard 5 is still stuck on `ch.qos.logback:logback-access:1.14.14` when `ch.qos.logback.access:logback-access-jetty12:2.0.6` exists - I wonder if migration might be in order?)~ > > Edit - I see this has already been...

#9970 should do the same as #9788 without reverting #8008 / #7965 behavior, not sure if DW team would want to do that until https://github.com/qos-ch/logback-access/pull/23 gets merged/released?