Mitchell Bösecke

Sounds like a reasonable feature to me

I'm not sure if this falls within the same request but my case would be satisfied by just being able to have consistent x-axis whenever I'm uploading a run. Run...

To be totally honest, my only reason for implementing this is to try and work around a bug with the CAS extension that occurs when geoserver is served over non-HTTPS;...

I've submitted my concerns with the CAS extension to [this ticket.](https://osgeo-org.atlassian.net/browse/GEOS-11202) The CAS extension has some flaws, and I've confirmed that in combination with the inability to run geoserver on...

I've now run `mvn spotless:apply` but squashed all my commits into one single one (hope that's okay).

For this work, I decided to use nested locks: ``` lock(metatile); try { for(tile : tiles){ executor.submit(() -> { lock(tile); try { // ... do work } finally { unlock(tile);...

I've committed some changes: * The thread pool now defaults to "number of cores * 2" * I added a setting on the "Caching Defaults" page to allow the user...

I separated encoding and saving into independent runnables and the primary ConveyorTile that was requested from the user is now encoded on the main thread but saved asynchronously. The additional...

Thanks for looking into that further. Just FYI, I've been distracted lately with other things but I'm hoping to revisit this further in the coming week or two! I haven't...