Repository navigation
build(deps): bump zstd-jni from 1.5.2-2 to 1.5.2-3 - #6
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [zstd-jni](https://github.com/luben/zstd-jni) from 1.5.2-2 to 1.5.2-3. - [Release notes](https://github.com/luben/zstd-jni/releases) - [Commits](luben/zstd-jni@v1.5.2-2...v1.5.2-3) --- updated-dependencies: - dependency-name: com.github.luben:zstd-jni dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
the
dependencies
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
Bot
deleted the
dependabot/maven/com.github.luben-zstd-jni-1.5.2-3
branch
May 20, 2022 14:18
4 tasks done
astubbs
added a commit
that referenced
this pull request
Aug 25, 2026
…y, races, records Six findings from the nine-persona code review of the commit-failure seam, applied and verified together (seam suites 69/69, full core unit suite 445/445, gates green): - Transaction recovery now recognises a commit that landed AFTER its budget was spent: the producer is READY, so there is nothing to complete or abort, and the old two-way complete-else-abort branch would have called abortTransaction() on READY - an invalid-transition KafkaException that escaped the seam's catch and fatally closed PC in the most benign case there is (the commit succeeded). The READY case is checked first and also caught defensively out of the abort call; recovery re-syncs ProducerWrapper's tracked state, which nothing else would. Two regression tests pin both routes (review finding #5, correctness + adversarial, validator-confirmed). - The seam's accounting fields (assignment epoch, streak, last-success times, the committer's deferral streak) were volatile ints with non-atomic increments and THREE writer sites across two threads - SpotBugs flagged five of them. They are now immutable generations swapped through a single AtomicReference per owner, so a rebalance reset can no longer be lost under a racing exhaustion, and a CommitFailureContext is built from the one generation its exhaustion produced - epoch and streak can no longer mix across an assignment boundary (finding #8). - CommitFailureHandler's javadoc claimed control-thread invocation; it actually runs on the dedicated pc-commit-failure-handler daemon thread, one at a time in failure order, 30s-bounded, fail-safe SHUT_DOWN on overrun/throw/null (finding #7). - The two commit-outage ITs declared class @Timeouts BELOW the worst-case sum of their own sequential Awaitility ceilings (300s vs 420s; 420s vs 960s), so a slow-but-correct run would be killed by JUnit mid-scenario instead of failing an assertion. Timeouts raised with the arithmetic recorded beside them; every atMost() and assertion untouched (finding #10). - docs/inflight/release-0.6.0.0.md now records the transactional path's give-up type change (InternalRuntimeException after 200 attempts -> public OffsetCommitBudgetExceededException on budget exhaustion) beside the existing #204 sync-path note (finding #9), and the candidate-ranking register drops its entry for the seam work landing with this branch, whose note this branch deletes (finding #6). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016jCtV2yqQvxDR6cLML8J8a
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
1 participant
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.
Bumps zstd-jni from 1.5.2-2 to 1.5.2-3.
Commits
c983ae3Adjust signature comments after e5c6a3290b8335db7c70877fda22ca26a96c72e4.510bbd6Add methods for streaming (de)compression of direct ByteBuffers.62b9dadFix lgtm C++.73ae46ev1.5.2-3e5c6a32Fix overflows54d3d50Fix some error return codes.b788a2eUpgrade scala.3106093Add NoFinalizer variants for the direct buffer streams.Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)