Nighly feedstock build failed about conda-forge-nightly-controller

[jdblischak]

I confirmed that rearranging the channel order (#27) fixed the nightly tiledb-py-feedstock build

https://dev.azure.com/TileDB-Inc/CI/_build/results?buildId=36951&view=results

[github-actions]

Nightly feedstock build failure for TileDB-Py%20Feedstock%20Testing at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=5&_a=summary

[ihnorton]

First run failed to solve libtiledb

-   - package tiledb-2.19.0.2023_12_02-h962fada_0 is excluded by strict repo priority

[github-actions]

Nightly feedstock build failure for TileDB-Py%20Feedstock%20Testing at https://dev.azure.com/TileDB-Inc/CI/_build?definitionId=5&_a=summary

[jdblischak]

I confirmed the solver error locally:

# strict
mamba create --dry-run -n test-strict \
  --override-channels \
  -c conda-forge -c tiledb/label/nightlies \
  --strict-channel-priority \
  'tiledb=*.2023_12_03'
## warning  libmamba Problem type not implemented SOLVER_RULE_STRICT_REPO_PRIORITY
## Could not solve for environment specs
## The following package could not be installed
## └─ tiledb *.2023_12_03**  is not installable because it conflicts with any installable versions previously reported.

# flexible
mamba create --dry-run -n test-strict \
  --override-channels \
  -c conda-forge -c tiledb/label/nightlies \
  --no-channel-priority \
  'tiledb=*.2023_12_03'
## + tiledb           2.19.0.2023_12_03  h2f72608_0        tiledb/label/nightlies        6MB

# strict, but rearrange channel order
mamba create --dry-run -n test-strict \
  --override-channels \
  -c tiledb/label/nightlies -c conda-forge  \
  --strict-channel-priority \
  'tiledb=*.2023_12_03'
## + tiledb           2.19.0.2023_12_03  h2f72608_0        tiledb/label/nightlies        6MB

The solution is to change the channel order. I'll send a PR soon

conda-forge-nightly-controller/scripts/update-channels.sh

Lines 9 to 10 in 3098d16

	# Add tiledb as source channel
	echo -e "channel_sources:\n - conda-forge,tiledb/label/nightlies" >> "$repo/recipe/conda_build_config.yaml"

Though I'm puzzled how this ever could have worked. Vivian/Seth added strict channel priority to the TileDB-Py feedstock on 2022-08-02, and I created my prototype in Oct 2022. My only guess is that maybe the feedstock builds were failing for other reasons at the time. Unsure since the Azure build logs aren't kept that long