bug: devcontainer is missing GDAL about ibis HOT 14 CLOSED

for kicks I pasted in the traceback above and asked the new Llama 3 for a solution...

it actually gave a nice explanation and something that worked (!)

amending the update content script to:

POETRY_DYNAMIC_VERSIONING=false python3 -m pip install -e '.[clickhouse,duckdb,clickhouse,examples,geospatial]'

got around the dunamai issue

So the two parts of the fix are probably:

1. add a Dockerfile under .devcontainer something like:

FROM mcr.microsoft.com/vscode/devcontainers/python:3.11

RUN apt-get update && apt-get install -y --no-install-recommends libgdal-dev

2. prepend POETRY_DYNAMIC_VERSIONING=false to the pip install -e

from ibis.

@anentropic Thanks for reporting this.

I'm not quite sure what's going on, because the geospatial dependencies were added recently, see #8837 and it looks like you are running on main.

@cpcloud any idea what could be going on here?

from ibis.

A local vs code environment a codespace are not the same. If a package attempting to call gdal-config that means it's being built from source, which means the wheel for whatever platform + python version you're using doesn't exist.

from ibis.

I don't think it's a local versus remote issue.

I also don't really understand how this works. Does the codespace run on GitHub infrastructure and VS code just "points" at that?

from ibis.

I don't think anyone's used the devcontainer setup locally, but it works on GitHub codespaces. I use it from time to time to try things that I don't want to run locally.

from ibis.

I believe it's running a docker container locally on my machine

from the terminal I get:

vscode ➜ /workspaces/ibis (main) $ arch
aarch64
vscode ➜ /workspaces/ibis (main) $ uname -a
Linux b66611250c8b 6.6.22-linuxkit #1 SMP Fri Mar 29 12:21:27 UTC 2024 aarch64 GNU/Linux

which makes sense as I'm on an M2 macbook

from ibis.

RuntimeError: Detected Git repository, but failed because of dubious ownership

Not entirely sure whether this will be possible to deal with. Speculating here, but I think this is probably related to how volumes are being mounted inside the container.

from ibis.

That error is also happening in dunamai which is a dependency of many many things.

I think we probably need someone who develops using a Mac to debug this

from ibis.

Hey @anentropic -- want to give it another shot now and see if it works?

from ibis.

Hi @gforsyth, I had to make a few tweaks to get the devcontainer to run and those changes are in #9019.

from ibis.

Hey @anentropic -- want to give it another shot now and see if it works?

Not working yet but looks like #9019 will fix it (needs the change in devcontainer.json to actually use the Dockerfile)

from ibis.

Just merged that, give it another go if you can!

from ibis.

Apologies, but it seems POETRY_DYNAMIC_VERSIONING=false was a hallucination by the LLM

I tried it and it appeared to work (i.e. by entering that line manually in terminal of a failed container launch)

but it doesn't work when (re)building the container from scratch ...I tried again just now and same thing. (And I can't find evidence for it via Google or GitHub search)

I'm not sure what devcontainers is doing to make the two scenarios behave differently

According to poetry-dynamic-versioning plugin docs a correct env var to disable active versioning would be POETRY_DYNAMIC_VERSIONING_BYPASS='8.0.0' i.e. specifying a static version value

I tried this and took care to make devcontainers rebuild the image with it and it seems to work

from ibis.

PR to fix the hallucination: #9031

from ibis.