Harm Verhagen

Raised as issue too in influxdb2 If you want influxdb-python to handle influxdb2 versions with this problem, this ticket needs to be fixed on influxdb-python too.

workaround, without changing influxdb-python code: pass headers to force use of json instead of MessagePack ``` # workaround for https://github.com/influxdata/influxdb/issues/23146 # influxdb-python crashes when issuing request to influxdb, as it...

I managed to find out what was the root cause here. (Not sure how to fix though). dango-channels (`async_to_sycn()` more specifically) does not work nice together with the connection pooling...

Note workaround as mentioned in #9 does work, if I set export TZ=Europe/Amsterdam before running uwsgi-sloth start, then I do get output in latest_5mins.html. But then the rendered html files...

DOCKER_BUILDKIT=1 gives the same results: Huge dir > 800MB instead of 30MB ``` $ DOCKER_BUILDKIT=1 docker build -f Dockerfile . -t postgis:test ... snipped lines => [stage-1 12/16] COPY --from=builder...

Hm... Reading through your comments I know realize that: My initial report is not correct. Although you don't have a multi-stage build image, you do have a nice clean-up step,...

Interestingly, it might be the case that libLLVM is not needed at all to run. I seem to be able to startup (and use) postgis perfectly fine when manually removing...

Suggested to postgres to drop llvm from runDeps See: https://github.com/docker-library/postgres/issues/1044

Anyway I think postgis would benefit from a multi-stage build in its Dockefile. In that case you never depend on whether of not your build steps requires libraries version that...

>imho: "Breaking change" is not good for existing users, so I would be very careful about that. In the future, it is expected that the https://github.com/postgis/docker-postgis/issues/293 and this will lead...