Repository navigation
build(deps): bump junit-pioneer from 1.9.1 to 2.0.1 - #588
Closed
dependabot[bot] wants to merge 440 commits into
Closed
dependabot[bot] wants to merge 440 commits into
dependabot[bot] wants to merge 440 commits into
Conversation
squash: turn down size of high volume test and remove Isolated from mult instance reblaance
squash-fix: Add missing resource lock to static state accessing test
Dont share collections in test and synchronise collection access.
…ulation Elapsed duration was truncating ms, cause frequency check to always return ok - causing the spin lock on commits
Running tests in parallel on jenkins puts a lot more load on it - ease up on requirements. Longer delay for chance to rebalance. Assert no concurrent exception instead of catching.
Experiencing some failures in Jenkins environment.
Add support for managed executor service
`find ./ -type f -print0 | xargs -0 dos2unix --`
Fixes #60 - upgrade AK to 2.7.0. Adds 2.7.0 as a stable build.
This messes with the shutdown process of the Producer, i.e. committing final transactions, offsets etc.
…ncy issues under high pressure
…itions are revoked (#548) * Fix deadlock on partitions revoked * Add unit test for rebalance deadlock on EoS * Update changelog and readme * merge with master changes * Fix misplaced comment
Bumps `mockito.version` from 4.9.0 to 5.1.1. Updates `mockito-core` from 4.9.0 to 5.1.1 - [Release notes](https://github.com/mockito/mockito/releases) - [Commits](mockito/mockito@v4.9.0...v5.1.1) Updates `mockito-junit-jupiter` from 4.9.0 to 5.1.1 - [Release notes](https://github.com/mockito/mockito/releases) - [Commits](mockito/mockito@v4.9.0...v5.1.1) --- updated-dependencies: - dependency-name: org.mockito:mockito-core dependency-type: direct:development update-type: version-update:semver-major - dependency-name: org.mockito:mockito-junit-jupiter dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: John Byrne <33546417+johnbyrnejb@users.noreply.github.com>
Bumps `vertx.version` from 4.3.6 to 4.4.1. Updates `vertx-web-client` from 4.3.6 to 4.4.1 Updates `vertx-junit5` from 4.3.6 to 4.4.1 --- updated-dependencies: - dependency-name: io.vertx:vertx-web-client dependency-type: direct:production update-type: version-update:semver-minor - dependency-name: io.vertx:vertx-junit5 dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [versions-maven-plugin](https://github.com/mojohaus/versions) from 2.14.1 to 2.15.0. - [Release notes](https://github.com/mojohaus/versions/releases) - [Changelog](https://github.com/mojohaus/versions/blob/master/ReleaseNotes.md) - [Commits](mojohaus/versions@2.14.1...2.15.0) --- updated-dependencies: - dependency-name: org.codehaus.mojo:versions-maven-plugin dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [threeten-extra](https://github.com/ThreeTen/threeten-extra) from 1.7.1 to 1.7.2. - [Release notes](https://github.com/ThreeTen/threeten-extra/releases) - [Commits](ThreeTen/threeten-extra@v1.7.1...v1.7.2) --- updated-dependencies: - dependency-name: org.threeten:threeten-extra dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* Avoid expensive calculation of properties for debug / trace logging when debug / trace logging is not enabled. --------- Co-authored-by: Lenne Hendrickx <lenne.h@sparkcentral.com>
Bumps [maven-release-plugin](https://github.com/apache/maven-release) from 3.0.0-M7 to 3.0.1. - [Release notes](https://github.com/apache/maven-release/releases) - [Commits](apache/maven-release@maven-release-3.0.0-M7...maven-release-3.0.1) --- updated-dependencies: - dependency-name: org.apache.maven.plugins:maven-release-plugin dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…nkins (#583) * update dependencies * add maven wrapper * Update jenkinsfile to use mvnw * Add to changelog
dependabot
Bot
added
the
dependencies
* update dependencies
Bumps [junit-pioneer](https://github.com/junit-pioneer/junit-pioneer) from 1.9.1 to 2.0.1. - [Release notes](https://github.com/junit-pioneer/junit-pioneer/releases) - [Commits](junit-pioneer/junit-pioneer@v1.9.1...v2.0.1) --- updated-dependencies: - dependency-name: org.junit-pioneer:junit-pioneer dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/maven/org.junit-pioneer-junit-pioneer-2.0.1
branch
from
June 20, 2023 14:37
40a6c17 to
a2607ca
Compare
* add instance id into thread name * Add instance id to thread name if possible --------- Co-authored-by: lixy <lixy@tuya.com> Co-authored-by: Edward Vaisman <10497078+eddyv@users.noreply.github.com>
* workerThreadPool is initialized lazily * workerThreadPool is initialized lazily - guava is removed * workerThreadPool is initialized lazily - license is updated * workerThreadPool is initialized lazily - license is updated - part 2 --------- Co-authored-by: pawel.wesolowski <p.weso271@gmail.com> Co-authored-by: Edward Vaisman <10497078+eddyv@users.noreply.github.com>
Bumps [reactor-core](https://github.com/reactor/reactor-core) from 3.5.1 to 3.5.7. - [Release notes](https://github.com/reactor/reactor-core/releases) - [Commits](reactor/reactor-core@v3.5.1...v3.5.7) --- updated-dependencies: - dependency-name: io.projectreactor:reactor-core dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: John Byrne <33546417+johnbyrnejb@users.noreply.github.com>
* adding in check for drain state * adding tests
Bumps `junit.version` from 5.10.0-M1 to 5.10.0-RC1. Updates `junit-jupiter-api` from 5.10.0-M1 to 5.10.0-RC1 - [Release notes](https://github.com/junit-team/junit5/releases) - [Commits](junit-team/junit-framework@r5.10.0-M1...r5.10.0-RC1) Updates `junit-jupiter-engine` from 5.10.0-M1 to 5.10.0-RC1 - [Release notes](https://github.com/junit-team/junit5/releases) - [Commits](junit-team/junit-framework@r5.10.0-M1...r5.10.0-RC1) Updates `junit-jupiter-params` from 5.10.0-M1 to 5.10.0-RC1 - [Release notes](https://github.com/junit-team/junit5/releases) - [Commits](junit-team/junit-framework@r5.10.0-M1...r5.10.0-RC1) --- updated-dependencies: - dependency-name: org.junit.jupiter:junit-jupiter-api dependency-type: direct:production update-type: version-update:semver-patch - dependency-name: org.junit.jupiter:junit-jupiter-engine dependency-type: direct:production update-type: version-update:semver-patch - dependency-name: org.junit.jupiter:junit-jupiter-params dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [guava](https://github.com/google/guava) from 32.0.1-jre to 32.1.1-jre. - [Release notes](https://github.com/google/guava/releases) - [Commits](https://github.com/google/guava/commits) --- updated-dependencies: - dependency-name: com.google.guava:guava dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps `vertx.version` from 4.4.3 to 4.4.4. Updates `vertx-web-client` from 4.4.3 to 4.4.4 Updates `vertx-junit5` from 4.4.3 to 4.4.4 --- updated-dependencies: - dependency-name: io.vertx:vertx-web-client dependency-type: direct:production update-type: version-update:semver-patch - dependency-name: io.vertx:vertx-junit5 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps `junit.platform.version` from 1.10.0-M1 to 1.10.0-RC1. Updates `junit-platform-launcher` from 1.10.0-M1 to 1.10.0-RC1 - [Release notes](https://github.com/junit-team/junit5/releases) - [Commits](https://github.com/junit-team/junit5/commits) Updates `junit-platform-commons` from 1.10.0-M1 to 1.10.0-RC1 - [Release notes](https://github.com/junit-team/junit5/releases) - [Commits](https://github.com/junit-team/junit5/commits) --- updated-dependencies: - dependency-name: org.junit.platform:junit-platform-launcher dependency-type: direct:development update-type: version-update:semver-patch - dependency-name: org.junit.platform:junit-platform-commons dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
|
|
Contributor
Author
|
A newer version of org.junit-pioneer:junit-pioneer exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged. |
Charles Provencher (cprovencher)
force-pushed
the
master
branch
from
November 3, 2023 18:14
075b4f9 to
558d599
Compare
Contributor
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/org.junit-pioneer-junit-pioneer-2.0.1
branch
November 3, 2023 18:14
Antony Stubbs (astubbs)
added a commit
to astubbs/parallel-consumer
that referenced
this pull request
Sep 2, 2026
…TS, so build
Antony asked for the Backlog.md comparison to be re-run just before merge, because the
2026-09-01 survey was written while this tool was still a proposal. It is re-run, and it
moved the answer - not by finding new features but by finding that the feature everyone
had matched up is the opposite operation.
THIS TIME IT WAS DRIVEN, NOT READ. The earlier pass opened by declaring itself
documentary and breaking docs/agent-harness.md's standing rule on purpose. This one
installs Backlog.md 1.50.1 transiently with npx into a throwaway repository - nothing
global, nothing on PATH - and provokes the case: a task on main, two branches editing it,
one marking it Done 80 seconds later.
THE RESULT NO READING WOULD HAVE PRODUCED. Standing on main with checkActiveBranches at
its default, `task list` shows main's copy only; the CLI says so itself, "Task lookups
read only the local working copy". `board export` DOES cross branches - it finds the two
tasks that exist only on feat/a - and it puts the shared task in To Do while the newest
version of it anywhere says Done. Nothing in any output says the branches disagree. Their
source names the mechanism without embarrassment: the selection function is `chooseWinners`.
So its cross-branch layer is drift SUPPRESSION, and that is the correct design for a
Kanban board where a task has one true state. docs/inflight/AGENTS.md chose the opposite
premise in as many words - "two branches can disagree about what is open" - and `note
drift` exists to report the disagreement. Same words, opposite operations. On this
repository the gap is measurable: bug-857-family.md has 25 versions carrying content
master has never held, across 80 refs. A reconciler answers with one.
FOUR RETRACTIONS, and the earlier pass already retracted three of its own, which is the
licence for these rather than a reason to think it is now finished.
- "Backlog.md already does the tracker half, including the cross-branch part" -
withdrawn, in ci-node-query-client.md where it lives.
- "The default now on adopt, because it ships" - withdrawn for the cross-branch reader
only. Untouched for the hooks half, which this pass did not re-examine.
- Section 10 OVER-corrected section 8. The axis is not location (beside the code versus
beside the agent) but AUTHORITY: whether a branch may disagree. Backlog.md is in-tree
AND single-truth; nothing surveyed is in-tree and multi-truth.
- "P1 is a position in a queue" is overstated. `priorities` is a configurable, ordered,
VALIDATED vocabulary - resolvePriorityValue rejects anything outside it - so the
impact names and their signal-integrity-first order would survive. What does not is
the type PARTITION (bug impacts and task impacts are separate sets here for a recorded
reason), the closed label set (theirs unions config with whatever tasks carry), and
the free-text reason on `deferred - after v6`.
THE EXPECTED FINDING THAT THE MEASUREMENT REFUSED, recorded because it is worth more than
the ones that landed. activeBranchDays defaults to 30 and 152 of this repo's 436 refs have
no commit in 30 days, which looked like a disqualifier. It is not: of 594 documents under
docs/ absent from origin/master, exactly ONE lives only on such a ref, and of 410 absent
in-flight notes, none do.
WHAT ELSE MOVED SINCE 2026-09-01, all re-queried rather than restated. Backlog.md 1.50.1,
6,603 stars, head commit dated 2026-09-02. Their #231 (GitHub sync), #456 (lifecycle
hooks) and confluentinc#588 (Beads integration) are all still closed NOT_PLANNED, untouched since
2026-07-01, and a search of their tracker finds no newer GitHub-integration issue. Beads
is architecturally unchanged - Dolt in refs/dolt/data. sd0xdev/sd0x-dev-flow has been
RENAMED to sd0xdev/sd0x-harness; the old URL redirects, so no citation needs repairing.
AND TWO THINGS THAT SHIPPED WHICH THE EARLIER PASS DID NOT NAME, both found by driving the
CLI rather than reading it: `onStatusChange`, a per-task shell callback that exists even
though the comprehensive hook system was declined; and `backlog cleanup`, which is a
compaction analogue - so compaction is not the thing only Beads has.
RECOMMENDATION: build, do not adopt, for the query layer, high confidence, and the reason
is not a feature count. What would change it is written falsifiably in section 9 - chiefly
a command of theirs that names the disagreeing versions instead of picking one. The verdict
is entered in process-adopt-external-harness.md, which owns the decision and keeps it
deferred until after v6; this does not un-defer anything.
NOT VERIFIED, said as loudly as the findings. Beads was not run - probe 1 of the earlier
section 6, does bd follow the git branch, is still open and process-beads-evaluation.md
still owns it. The probe used local branches with no remote. Three tasks in a fresh
repository is not 436 refs. And section 5's schema verdict is derived from their source,
not from an attempted migration, which makes it the weakest claim in the document.
Six gates green, and bin/check-all.sh: 15 passed, 0 failed.
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
20 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.
Bumps junit-pioneer from 1.9.1 to 2.0.1.
Release notes
Sourced from junit-pioneer's releases.
... (truncated)
Commits
cdfa678Make StdIn report available bytes (#725 / #728)1f07395Update Gradle, Java, plugins, and dependencies (#729, #726 / #727)3f8392fSet JPMS module version (#713 / #716)10b91cbFix typo to let the warning render correctly (#710)4e3c7edUpdate actions/checkout and actions/setup-java v2 to v3 (#702)cc2e431Update Gradle Wrapper to 7.6 (#693 / #694)17004dbDepose Nicolai as benevolent dictator (#683 / #684)0037f1cUpdate required Java version to 11 (#617 / #627)b9dc377Replace Locale constructor by Locale builder (#658 / #662)c1fc386Remove CartesianTest extension v1 (#517 / #635)You can trigger a rebase of this PR 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)