forked from TileDB-Inc/TileDB
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[pull] dev from TileDB-Inc:dev #144
Merged
Merged
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
This is part2 of #4516 , adding the `rest_client` part. The REST route needs to be added on the Cloud side (the actual route needs confirmation/specification from the Cloud team). --- TYPE: FEATURE DESC: Query Plan REST support - part 2: rest client
This is part2 of #4534 , adding the `rest_client` part. --- TYPE: FEATURE DESC: Consolidation Plan REST support - part 2: rest client
--- TYPE: NO_HISTORY DESC: Update dev HISTORY with 2.19 and 2.20 patch content.
--- TYPE: NO_HISTORY DESC: Bump dev version to 2.22.0.
* Move unit filter pipeline tests from tiledb_unit to unit tests in tiledb/sm/filter/tests. * Rename file with remaining C++ integration tests. --- TYPE: NO_HISTORY --------- Co-authored-by: Ypatia Tsavliri <[email protected]>
Add a test for concurrent array metadata writes. With the fragment name generation, this test is tagged as `[!mayfail]`, because there's no means of sorting fragments which are written within the same millisecond. Once sub millisecond temporal disambiguation is implemented, this test should serve as a regression case. --- TYPE: NO_HISTORY DESC: Add a test for concurrent array metadata writes. --------- Co-authored-by: KiterLuc <[email protected]>
This PR fixes these concerns with release artifact filenames: 1. Windows having `amd64` in name instead of `x86_64` 2. Package name missing full tag as name 3. Package name missing commit hash Number 1. is fixed by checking CMake variabe CMAKE_SYSTEM_PROCESSOR and if its set to `AMD64` the packaging logic uses `x86_64` instead. Number 2. and 3. are fixed by packaging process requiring `TILEDB_PACKAGE_VERSION` environment variable to be present when calling packaging commands (`make package` or `cpack ...` or similar) An example pipeline in my fork: https://github.com/dudoslav/TileDB/actions/runs/8266657611 An example release `t14` in my fork: https://github.com/dudoslav/TileDB/releases/tag/t14 (Please wait for them to finish) --- TYPE: NO_HISTORY DESC: Fix CPack packaging issues with file name format
After changing release artifact names the `releases.csv` file generator logic broke since the REGEX matcher expected different input. This PR changes the matcher REGEX to match everything after all required fields:  example release: https://github.com/dudoslav/TileDB/releases/tag/t15.0.1-rc1 --- TYPE: NO_HISTORY DESC: Change regex matching release artifacts
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.
See Commits and Changes for more details.
Created by
pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )