Bump WolverineFx and WolverineFx.RuntimeCompilation - #2301
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Bump WolverineFx and WolverineFx.RuntimeCompilation#2301dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps WolverineFx from 6.29.1 to 6.29.2 Bumps WolverineFx.RuntimeCompilation from 6.29.1 to 6.29.2 --- updated-dependencies: - dependency-name: WolverineFx dependency-version: 6.29.2 dependency-type: direct:production update-type: version-update:semver-patch - dependency-name: WolverineFx.RuntimeCompilation dependency-version: 6.29.2 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
.NET
Contributor
Author
|
Superseded by #2312. |
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.
Updated WolverineFx from 6.29.1 to 6.29.2.
Release notes
Sourced from WolverineFx's releases.
6.29.2
A fix release. Four changes, three of them reported bugs.
RavenDB users should take this one
ClearAllAsyncdeleted node records by tracked entity from a session that had never loaded them, so a Solo-mode start after a Balanced-mode run threwInvalidOperationException: WolverineNode is not associated with the sessionon every stale node and the application could not start at all. The workaround of clearingWolverineNodesby hand in RavenDB Studio is no longer needed. (#3993, closes #3986)The compliance coverage written for that fix caught a second provider: SQLite orphaned every agent assignment row, because its assignment table has no
ON DELETE CASCADE(PostgreSQL, Sql Server and Oracle do). The orphans stay invisible until a node re-registers under the same id — the GH-3604 ejection path — where it returns owning agents it was never reassigned. The underlying gap was thatNodePersistenceCompliancenever exercisedClearAllAsyncat all, which is how two providers shipped it broken. It does now.Agents no longer stall on a node that cannot build them
When
IAgentFamily.BuildAgentAsyncthrew, the leader saw only an unconfirmed agent — which it deliberately does not treat as a failure — so the assignment stood and the same agent was requested on the same failing node forever. Reported as a 54-minute fleet-wide projection stall on a blue/green cluster with disjoint projection versions. Consecutive failed starts are now counted on the node that catches them and feed into the existing GH-3888 release path. NewDurabilitySettings.MaxAgentStartFailuresBeforeRelease(default3); set it to0for the previous behaviour. (#3994, closes #3970)The orphaned-message sweep no longer dominates database load
Reported against a 466-shard PostgreSQL deployment. The sweep's predicate could not use an index, so it full-scanned the whole inbox per database every five seconds to find nothing; the update was unbounded, so one node loss became a single ~910,000-row rewrite across the fleet; and it ran inside the shared recovery transaction, blocking inbox inserts. All three are fixed, with a new
OrphanedMessageReleaseBatchSizeand a dedicatedOrphanedMessageSweepPollingTime. (#3995, closes #3971)HTTP endpoints can take immutable request types
A
Before/BeforeAsyncmethod on an endpoint class that accepts the request type and returns it now replaces the request body for the rest of the chain, exactly as it has on the handler side since GH-516. Use it to stamp server-supplied values onto an immutablerecordrequest before the endpoint runs. (#3984)Full detail for every item is in CHANGELOG.md.
What's Changed
New Contributors
Full Changelog: JasperFx/wolverine@V6.29.1...V6.29.2
Commits viewable in compare view.
Updated WolverineFx.RuntimeCompilation from 6.29.1 to 6.29.2.
Release notes
Sourced from WolverineFx.RuntimeCompilation's releases.
6.29.2
A fix release. Four changes, three of them reported bugs.
RavenDB users should take this one
ClearAllAsyncdeleted node records by tracked entity from a session that had never loaded them, so a Solo-mode start after a Balanced-mode run threwInvalidOperationException: WolverineNode is not associated with the sessionon every stale node and the application could not start at all. The workaround of clearingWolverineNodesby hand in RavenDB Studio is no longer needed. (#3993, closes #3986)The compliance coverage written for that fix caught a second provider: SQLite orphaned every agent assignment row, because its assignment table has no
ON DELETE CASCADE(PostgreSQL, Sql Server and Oracle do). The orphans stay invisible until a node re-registers under the same id — the GH-3604 ejection path — where it returns owning agents it was never reassigned. The underlying gap was thatNodePersistenceCompliancenever exercisedClearAllAsyncat all, which is how two providers shipped it broken. It does now.Agents no longer stall on a node that cannot build them
When
IAgentFamily.BuildAgentAsyncthrew, the leader saw only an unconfirmed agent — which it deliberately does not treat as a failure — so the assignment stood and the same agent was requested on the same failing node forever. Reported as a 54-minute fleet-wide projection stall on a blue/green cluster with disjoint projection versions. Consecutive failed starts are now counted on the node that catches them and feed into the existing GH-3888 release path. NewDurabilitySettings.MaxAgentStartFailuresBeforeRelease(default3); set it to0for the previous behaviour. (#3994, closes #3970)The orphaned-message sweep no longer dominates database load
Reported against a 466-shard PostgreSQL deployment. The sweep's predicate could not use an index, so it full-scanned the whole inbox per database every five seconds to find nothing; the update was unbounded, so one node loss became a single ~910,000-row rewrite across the fleet; and it ran inside the shared recovery transaction, blocking inbox inserts. All three are fixed, with a new
OrphanedMessageReleaseBatchSizeand a dedicatedOrphanedMessageSweepPollingTime. (#3995, closes #3971)HTTP endpoints can take immutable request types
A
Before/BeforeAsyncmethod on an endpoint class that accepts the request type and returns it now replaces the request body for the rest of the chain, exactly as it has on the handler side since GH-516. Use it to stamp server-supplied values onto an immutablerecordrequest before the endpoint runs. (#3984)Full detail for every item is in CHANGELOG.md.
What's Changed
New Contributors
Full Changelog: JasperFx/wolverine@V6.29.1...V6.29.2
Commits viewable in compare view.
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 show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@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)