The nightly build job failed on Saturday (2026-04-04)

[github-actions]

The nightly build job failed on Saturday (2026-04-04) in run 23970633792

[github-actions]

The nightly build job failed on Sunday (2026-04-05) in run 23993796571

[github-actions]

The nightly build job failed on Monday (2026-04-06) in run 24018051554

[alancleary]

I used Claude to confirm that the issue is related to pybind11:

  Root cause confirmed: tiledb-py 0.36.0 (used for release-2.30) doesn't pin pybind11, so pip pulls the latest — pybind11 3.0.3. pybind11 3.0 changed py::make_tuple to return a strongly-typed pybind11::typing::Tuple<Types...> instead of a
  plain py::tuple.

  In tiledb-py's domain.cc, there's a lambda with multiple return py::make_tuple(dom.first, dom.second) branches that each return different concrete types (uint64_t, int64_t, uint32_t, etc.). With pybind11 2.x this was fine (all returned
  py::tuple); with pybind11 3.0 the compiler sees inconsistent deduced return types and errors out.

  The main tiledb-py works because it has presumably been updated for pybind11 3.0 compatibility.

  Fix options:

  1. Quick fix — pin pybind11 in build-tiledb-py.sh before the install:
  python -m pip install 'pybind11<3.0.0'
  python -m pip install -Cskbuild.cmake.define.TILEDB_REMOVE_DEPRECATIONS=OFF -v .
  2. Better fix — update the tiledb-py version in nightly.yml line 27 from 0.36.0 to a newer release that supports pybind11 3.0+, if one exists on the 0.36.x line.

@kounelisagis Is there any plan to make TileDB-Py compatible with pybind11 version 3+?

[github-actions]

The nightly build job failed on Tuesday (2026-04-07) in run 24063451860

[github-actions]

The nightly build job failed on Wednesday (2026-04-08) in run 24116832962

[github-actions]

The nightly build job failed on Thursday (2026-04-09) in run 24171472587

[kounelisagis]

Opened http://github.com/TileDB-Inc/TileDB-VCF/pull/883