tiledbsoma 1.9.0 pre check #110
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
March 26, 2024 13:03
…nda-forge-pinning 2024.03.26.11.57.11
|
Awesome! As I predicted, bumping tiledb 2.21 avoided the conda solver errors we previously observed in the nightly when building against tiledb 2.20 (#108) |
|
Closing per standard procedure |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Following our established procedure
Note: there is still one open TileDB-SOMA PR which is blocking 1.9.0: single-cell-data/TileDB-SOMA#2305
However, I want to flush out any lurking Conda-solver errors in parallel via this pre-check PR.
single-cell-data/TileDB-SOMA#2311