Dan Armbrust

no idea if this is related, I'm not really a jruby developer. But upgrading from 1.11.2 to 1.16.4 of bunder in our build process (jruby complete / jruby exec plugin...

I also noted from the dump above, it referenced the path /apps/.gem/jruby/2.3.0 This is a garbage path, that points to nowhere. This is a war file being deployed in tomcat...

I did a bit more isolation - 1.13.7 is the last version of bundler that worked for me. 1.14.6 does not work, nor does anything newer. I haven't attempted to...

It also isn't showing the original files, its showing scaled down versions, which sucks for big monitors. Where is the option to see the original, uploaded photo, full screen? Every...

 Wireshark capture of the response in question

fixed in the above commit on my fork, if you need a release, see https://github.com/Sagebits/hola/releases/tag/v0.2.4-sagebits also published to maven central as ``` net.sagebits hola 0.2.4-sagebits ```

fixed in the above commit on my fork, if you need a release, see https://github.com/Sagebits/hola/releases/tag/v0.2.4-sagebits also published to maven central as ``` net.sagebits hola 0.2.4-sagebits ```

This release on my fork should have been built with the jdk8 flags set properly. https://github.com/Sagebits/hola/releases/tag/v0.2.4-sagebits also published to maven central as ``` net.sagebits hola 0.2.4-sagebits ```

Same here on Ubuntu... going back from 0.2.3 to 0.2.1 made it work for me as well.

Appears to be one of these two commits that broke it: https://github.com/fflewddur/hola/commit/3dac52ee98ec9c0b8e0fa35dc6b18bc120f9d531 https://github.com/fflewddur/hola/commit/233c0c4a13dc034b1523f47ec71d85e872916b9f Probably a combination of the two, since they are both changing what happens in the RunOnce where...