David Manthey

Of course it can be mitigated downstream. I wasted quite a bit of time trying to figure out what was wrong with code when the problem was that girder_worker recommends...

It is useful to know that Celery 4.3 (particularly via girder_worker) is being used successfully with RabbitMQ. I'll make a PR for adding to the documentation to the effect of...

@12rambau Thanks for working on this.

I think there may be two issues here. First, if you use a girder_worker task with `.delay`, it is using the Celery app loaded from the girder_worker config files NOT...

@kotfic Either I've misconfigured things, or girder_worker on girder with a non-local rabbitmq instance requires the worker.*.cfg to be configured on both the worker and girder machines.

I think it was laziness on my part -- in the base tile source, the `tiledRegion_` file IS the output. In the gdal source, it is just a temp file,...

We really just want a unique temporary name that is guaranteed to be free and can be created, but we are using vips to write the first image and gdal...

Also, there are some rare cases where tiles are repeated (generally dull areas along the edges of an image). In this case, we could reference the same area in a...

See https://pillow.readthedocs.io/en/stable/reference/ImageCms.html#cmsprofile

See also https://github.com/ghsmith/SVSUtil