chore(release): prepare 0.16.1 - #865
Merged
Merged
Conversation
downloads_failed is bumped before the TransferEvent is pushed. The Windows CI run for 0.16.1 hit that race: 2070 tests passed and test_handle_prefetch_failure_records_v3_transfer_timestamps panicked on an empty recent_transfers deque. Poll for both the counter and the event, matching prefetch_import_failure_is_counted_as_failure.
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
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.
Summary
Version bump for the 0.16.1 release. Ships since v0.16.0:
Cacheability, C/C++ units that previously always missed:
-gfullvia the resolved probe-gdwarf-2via the resolved probe-fmerge-all-constants-fsanitize-undefined-strip-path-components=-1so aws-lc-sys 0.44 jitterentropy TUs cache (cc: cache aws-lc-sys jitterentropy builds using -fsanitize-undefined-strip-path-components=-1 #840)-mno-omit-leaf-frame-pointer(cc: cache debug builds using -mno-omit-leaf-frame-pointer #839)Correctness:
Robustness:
Also in the tree but not user-visible: docs rewrite (#863), OpenDAL and Lance nightly benchmarks (#864, #859), CODEOWNERS for private-runner workflows (#862), test and CI work (#855, #853, #846, #833, #831).
Patch bump: #860 and #851 are labelled
feat, but both only add flag keying that turns previously-uncacheable translation units into cacheable ones. No API or behaviour change.Note:
crates/kache-proofsmoves from0.0.0to0.16.1. That crate landed in #855 after the last bump, so this is the first timecargo set-version --workspacehas swept it up. It ispublish = falseand outside the consistency gate, same askache-e2eandkache-service, which already track the workspace version.After merge: tag
v0.16.1on the merge commit to trigger the release.Checklist
just bump 0.16.1(cargo set-version --workspace, lock settled bycargo check)scripts/check-version-consistency.shpasses: kache == kache-core == kache-core dep-pin == 0.16.1cargo check --workspaceclean