Add default TileDB path setup for workflows when libtiledb_ref is not provided#2280
Merged
Merged
Conversation
ypatia
approved these changes
Nov 27, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The recent refactor in #2275 introduced support for building wheels against arbitrary
libtiledb_refvalues. However, this broke the default workflow behavior whenlibtiledb_refis not provided, causing wheel build failures on macOS and Windows. This PR fixes that by adding workflow steps to setTILEDB_LIB_PATHandTILEDB_BIN_PATHto$RUNNER_TEMP/tiledb-externalwhenlibtiledb_refis not provided.Errors:
FileNotFoundError: Unable to find library: tiledb.dll@rpath/libtiledb.dylib not foundProof workflow: https://github.com/TileDB-Inc/TileDB-Py/actions/runs/19714416387