Nightly feedstock build failed

[github-actions[bot]]

Nightly feedstock build failure for tiledbsoma-feedstock at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=43&_a=summary

[jdblischak]

The nightly builds started failing on Monday night

It's a new solver error, this time with r-tiledbsoma. Here is the solver error from the most recent nightly linux-64 failure:

    conda_libmamba_solver.exceptions.LibMambaUnsatisfiableError: Encountered problems while solving:
      - package libtiledbsoma-1.8.0.dev20240313-hc1eed26_1 requires spdlog >=1.11.0,<1.12.0a0, but none of the providers can be installed

    Could not solve for environment specs
    The following packages are incompatible
    ├─ libtiledbsoma ==1.8.0.dev20240313 hc1eed26_1 is installable and it requires
    │  └─ spdlog >=1.11.0,<1.12.0a0 , which can be installed;
    └─ spdlog ==1.12.0 hd2e6256_2 is not installable because it conflicts with any installable versions previously reported.

[github-actions[bot]]

Nightly feedstock build failure for tiledbsoma-feedstock at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=43&_a=summary

[github-actions[bot]]

Nightly feedstock build failure for tiledbsoma-feedstock at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=43&_a=summary

[github-actions[bot]]

Nightly feedstock build failure for tiledbsoma-feedstock at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=43&_a=summary

[jdblischak]

In #103, I confirmed the nightly error is going to prevent any future PRs. It is currently blocking #98

[jdblischak]

I think I have this mostly worked out.

Recall that about a month ago in #86, I pinned fmt=9 and spdlog=1.11 to unblock the deployment of tiledbsoma 1.7.1 to TileDB Cloud. In that PR I commented:

This will eventually cause other solver issues as conda-forge continues to migrate to fmt 10, but we can troubleshoot this in the future.

And that time is now 😄

I haven't pinpointed exactly which requirement of r-tiledbsoma is causing the conflict (unfortunately the solver didn't spit out all the packages it was trying to install), but presumably something is causing the problem.

Further complicating the situation is that now the conda-forge tiledb recipe properly depends on spdlog from conda-forge (https://github.com/conda-forge/tiledb-feedstock/pull/254), and thus it is pinned to the current conda-forge default of spdlog 1.12.

Note that the libtiledbsoma build passes because it installs a libtiledb 2.20.1 conda binary prior to it properly depending on the conda-forge spdlog

spdlog:                   1.11.0-h9b3ece8_1           conda-forge
tiledb:                   2.20.1-h7c1ff67_3           conda-forge

wget https://anaconda.org/conda-forge/tiledb/2.20.1/download/linux-64/tiledb-2.20.1-h7c1ff67_3.conda
conda inspect hash-inputs tiledb-2.20.1-h7c1ff67_3.conda
## {'tiledb-2.20.1-h7c1ff67_3.conda': {'recipe': {'aws_crt_cpp': '0.26.2',
##                                                'aws_sdk_cpp': '1.11.267',
##                                                'bzip2': '1',
##                                                'channel_targets': 'conda-forge '
##                                                                   'main',
##                                                'curl': '8',
##                                                'cxx_compiler': 'gxx',
##                                                'cxx_compiler_version': '12',
##                                                'libabseil': '20240116',
##                                                'libcurl': '8',
##                                                'libgoogle_cloud_devel': '2.22',
##                                                'libgoogle_cloud_storage_devel': '2.22',
##                                                'libxml2': '2',
##                                                'lz4_c': '1.9.3',
##                                                'openssl': '3',
##                                                'target_platform': 'linux-64',
##                                                'zlib': '1.2',
##                                                'zstd': '1.5'}}}

The latest conda-forge tiledb binaries are pinned to spdlog 1.12, and can't be installed in a conda env with 1.11

https://anaconda.org/conda-forge/tiledb/2.20.1/download/linux-64/tiledb-2.20.1-h99d63bd_4.conda
conda inspect hash-inputs tiledb-2.20.1-h99d63bd_4.conda
## {'tiledb-2.20.1-h99d63bd_4.conda': {'recipe': {'aws_crt_cpp': '0.26.3',
##                                                'aws_sdk_cpp': '1.11.267',
##                                                'bzip2': '1',
##                                                'channel_targets': 'conda-forge '
##                                                                   'main',
##                                                'curl': '8',
##                                                'cxx_compiler': 'gxx',
##                                                'cxx_compiler_version': '12',
##                                                'fmt': '10',
##                                                'libabseil': '20240116',
##                                                'libcurl': '8',
##                                                'libgoogle_cloud_devel': '2.22',
##                                                'libgoogle_cloud_storage_devel': '2.22',
##                                                'libxml2': '2',
##                                                'lz4_c': '1.9.3',
##                                                'openssl': '3',
##                                                'spdlog': '1.12',
##                                                'target_platform': 'linux-64',
##                                                'zlib': '1.2',
##                                                'zstd': '1.5'}}}

[jdblischak]

And I confirmed that both the UDF and notebook py39 images currently have fmt 9.1.0 and spdlog 1.11.0 installed in them

[github-actions[bot]]

Nightly feedstock build failure for tiledbsoma-feedstock at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=43&_a=summary