I discovered in #669 that tiledb.open() segfaults when using tiledb-py 0.26.0 from conda with the dev version of tiledb (currently 0.22.0). I tried updating the conda version, but it was constrained (presumably by the pyarrow pin). Anyways, I realized it probably makes more sense to use the dev version of tiledb-py when testing against the dev version of libtiledb. In fact, I had considered this when I first created the nightly build (https://github.com/TileDB-Inc/TileDB-VCF/pull/577#issuecomment-1723834866), but up until now it had been working without issue.
Also, I revisited the installation of the Python dependencies. Previously I installed the Python dependencies with conda on Ubuntu and pip on macOS, simply because that was the only way I could get them to work (https://github.com/TileDB-Inc/TileDB-VCF/pull/579#issuecomment-1747418594). I confirmed that now I can install the dependencies with pip on Ubuntu (and also migrate to pyarrow 11), so I consolidated the two jobs.
I discovered in #669 that
tiledb.open()segfaults when using tiledb-py 0.26.0 from conda with the dev version of tiledb (currently 0.22.0). I tried updating the conda version, but it was constrained (presumably by the pyarrow pin). Anyways, I realized it probably makes more sense to use the dev version of tiledb-py when testing against the dev version of libtiledb. In fact, I had considered this when I first created the nightly build (https://github.com/TileDB-Inc/TileDB-VCF/pull/577#issuecomment-1723834866), but up until now it had been working without issue.Also, I revisited the installation of the Python dependencies. Previously I installed the Python dependencies with conda on Ubuntu and pip on macOS, simply because that was the only way I could get them to work (https://github.com/TileDB-Inc/TileDB-VCF/pull/579#issuecomment-1747418594). I confirmed that now I can install the dependencies with pip on Ubuntu (and also migrate to pyarrow 11), so I consolidated the two jobs.