Repository navigation
fix: Bump dotnet-ef and 14 others - #31
Open
dependabot[bot] wants to merge 1 commit into
Open
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps dotnet-ef from 10.0.14 to 10.0.15 Bumps Microsoft.AspNetCore.DataProtection.StackExchangeRedis from 10.0.14 to 10.0.15 Bumps Microsoft.AspNetCore.OpenApi from 10.0.14 to 10.0.15 Bumps Microsoft.EntityFrameworkCore.Design from 10.0.14 to 10.0.15 Bumps Microsoft.EntityFrameworkCore.InMemory from 10.0.14 to 10.0.15 Bumps OpenTelemetry.Instrumentation.AspNetCore from 1.20.1 to 1.21.0 Bumps OpenTelemetry.Instrumentation.Http from 1.20.1 to 1.21.0 Bumps Scalar.AspNetCore from 2.18.6 to 3.0.1 Bumps StackExchange.Redis to 3.4.35 Bumps WolverineFx from 6.59.0 to 6.64.2 Bumps WolverineFx.EntityFrameworkCore from 6.59.0 to 6.64.2 Bumps WolverineFx.Postgresql from 6.59.0 to 6.64.2 Bumps WolverineFx.RabbitMQ from 6.59.0 to 6.64.2 Bumps WolverineFx.RuntimeCompilation from 6.59.0 to 6.64.2 Bumps xunit.v3 from 4.0.2 to 4.0.3 --- updated-dependencies: - dependency-name: xunit.v3 dependency-version: 4.0.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: dotnet-ef dependency-version: 10.0.15 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Microsoft.AspNetCore.DataProtection.StackExchangeRedis dependency-version: 10.0.15 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Microsoft.AspNetCore.OpenApi dependency-version: 10.0.15 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Microsoft.EntityFrameworkCore.Design dependency-version: 10.0.15 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Microsoft.EntityFrameworkCore.InMemory dependency-version: 10.0.15 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: OpenTelemetry.Instrumentation.AspNetCore dependency-version: 1.21.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget - dependency-name: OpenTelemetry.Instrumentation.Http dependency-version: 1.21.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget - dependency-name: Scalar.AspNetCore dependency-version: 3.0.1 dependency-type: direct:production update-type: version-update:semver-major dependency-group: nuget - dependency-name: StackExchange.Redis dependency-version: 3.4.35 dependency-type: direct:production update-type: version-update:semver-major dependency-group: nuget - dependency-name: StackExchange.Redis dependency-version: 3.4.35 dependency-type: direct:production update-type: version-update:semver-major dependency-group: nuget - dependency-name: StackExchange.Redis dependency-version: 3.4.35 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: WolverineFx dependency-version: 6.64.2 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget - dependency-name: WolverineFx.EntityFrameworkCore dependency-version: 6.64.2 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget - dependency-name: WolverineFx.Postgresql dependency-version: 6.64.2 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget - dependency-name: WolverineFx.RabbitMQ dependency-version: 6.64.2 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget - dependency-name: WolverineFx.RuntimeCompilation dependency-version: 6.64.2 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget - dependency-name: xunit.v3 dependency-version: 4.0.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget ... Signed-off-by: dependabot[bot] <support@github.com>
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 dotnet-ef from 10.0.14 to 10.0.15.
Release notes
Sourced from dotnet-ef's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.AspNetCore.DataProtection.StackExchangeRedis from 10.0.14 to 10.0.15.
Release notes
Sourced from Microsoft.AspNetCore.DataProtection.StackExchangeRedis's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.AspNetCore.OpenApi from 10.0.14 to 10.0.15.
Release notes
Sourced from Microsoft.AspNetCore.OpenApi's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.EntityFrameworkCore.Design from 10.0.14 to 10.0.15.
Release notes
Sourced from Microsoft.EntityFrameworkCore.Design's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.EntityFrameworkCore.InMemory from 10.0.14 to 10.0.15.
Release notes
Sourced from Microsoft.EntityFrameworkCore.InMemory's releases.
No release notes found for this version range.
Commits viewable in compare view.
Pinned OpenTelemetry.Instrumentation.AspNetCore at 1.21.0.
Release notes
Sourced from OpenTelemetry.Instrumentation.AspNetCore's releases.
1.21.0
NuGet: OpenTelemetry.Exporter.Geneva v1.21.0
Fixed an issue where, with
EnableOtlpProtobufEncoding=true, a metricattribute of type
ulongwith a value greater thanlong.MaxValuewasserialized incorrectly, causing the dimension to be dropped or the data point
to be malformed. Such values are now exported as their decimal string
representation, and an attribute that fails to serialize is now dropped
cleanly and reported through the exporter's
EventSource.(#5915)
Improved JSON numeric serialization throughput on .NET 10 and later by formatting
directly into the UTF-8 output buffer.
(#5941)
Breaking Change Dropped support for
net8.0andnet9.0.(#3867)
Add support for .NET 11.0.
(#3867)
Updated OpenTelemetry core component version(s) to
1.21.0.(#5969)
See CHANGELOG for details.
1.21.0-rc.1
NuGet: OpenTelemetry.Instrumentation.Process v1.21.0-rc.1
Updated Semantic Conventions version to
1.45.0.(#5833)
Breaking Change Dropped support for
net8.0andnet9.0.(#3867)
Add support for .NET 11.0.
(#3867)
Updated OpenTelemetry core component version(s) to
1.21.0.(#5969)
See CHANGELOG for details.
1.21.0-beta.1
NuGet: OpenTelemetry.Extensions.Enrichment v1.21.0-beta.1
Breaking Change Dropped support for
net8.0andnet9.0.(#3867)
Add support for .NET 11.0.
(#3867)
Updated OpenTelemetry core component version(s) to
1.21.0.(#5969)
See CHANGELOG for details.
1.21.0-alpha.1
NuGet: OpenTelemetry.Instrumentation.EventCounters v1.21.0-alpha.1
Breaking Change Dropped support for
net8.0andnet9.0.(#3867)
Add support for .NET 11.0.
(#3867)
Updated OpenTelemetry core component version(s) to
1.21.0.(#5969)
See CHANGELOG for details.
1.20.3
NuGet: OpenTelemetry.Extensions.AWS v1.20.3
Fixed
AddXRayTraceId()andAddXRayTraceIdWithSampler()not replacingtrace IDs when targeting .NET Framework or .NET Standard. The X-Ray ID
generator now uses
Activity.TraceIdGeneratoron all target frameworks.As a result,
AWSXRayIdGenerator.ReplaceTraceId()is now public on alltarget frameworks, and
AddXRayTraceIdWithSampler()andAWSXRayIdGenerator.ReplaceTraceId(Sampler)are now obsolete on alltarget frameworks.
(#5809)
No longer throw and catch an exception in
AWSXRayPropagatorfor anX-Amzn-Trace-Idheader with upper case or padded hexadecimal identifiers,or with a trace or parent identifier of all zeros.
(#5825)
Fixed
AWSXRayPropagatorusing the value of a field of theX-Amzn-Trace-Idheader whose name only starts with
Root,ParentorSampled.(#5825)
See CHANGELOG for details.
NuGet: OpenTelemetry.Instrumentation.AWS v1.20.3
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Instrumentation.AWSLambda v1.20.3
No notable changes.
See CHANGELOG for details.
1.20.2
NuGet: OpenTelemetry.Extensions.AWS v1.20.2
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Instrumentation.AWS v1.20.2
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Instrumentation.AWSLambda v1.20.2
server.addressandserver.portnot being recorded correctly for HTTPrequests with an IPv6 address in the
Hostheader (e.g.[::1]:8080).(#5788)
See CHANGELOG for details.
1.20.2-beta.1
NuGet: OpenTelemetry.Instrumentation.Hangfire v1.20.2-beta.1
Fixed failed jobs exporting the exception message as the span status description.
The message is now only recorded when
RecordExceptionis enabled.(#5884)
Fixed baggage from a job being visible to work started by other jobs
performed on the same worker.
(#5886)
Added
EnrichWithBackgroundJobandCustomStateMappingstoHangfireMetricsInstrumentationOptions. Use them to add custom attributes tothe metrics and to count jobs in custom Hangfire states.
(#5810)
Fixed
workflow.execution.durationfor theexecutingstate. It included thetime of other measurements of this instrumentation, for example the database
query that
RecordQueueLatencyadds.(#5810)
See CHANGELOG for details.
Commits viewable in compare view.
Pinned OpenTelemetry.Instrumentation.Http at 1.21.0.
Release notes
Sourced from OpenTelemetry.Instrumentation.Http's releases.
1.21.0
NuGet: OpenTelemetry.Exporter.Geneva v1.21.0
Fixed an issue where, with
EnableOtlpProtobufEncoding=true, a metricattribute of type
ulongwith a value greater thanlong.MaxValuewasserialized incorrectly, causing the dimension to be dropped or the data point
to be malformed. Such values are now exported as their decimal string
representation, and an attribute that fails to serialize is now dropped
cleanly and reported through the exporter's
EventSource.(#5915)
Improved JSON numeric serialization throughput on .NET 10 and later by formatting
directly into the UTF-8 output buffer.
(#5941)
Breaking Change Dropped support for
net8.0andnet9.0.(#3867)
Add support for .NET 11.0.
(#3867)
Updated OpenTelemetry core component version(s) to
1.21.0.(#5969)
See CHANGELOG for details.
1.21.0-rc.1
NuGet: OpenTelemetry.Instrumentation.Process v1.21.0-rc.1
Updated Semantic Conventions version to
1.45.0.(#5833)
Breaking Change Dropped support for
net8.0andnet9.0.(#3867)
Add support for .NET 11.0.
(#3867)
Updated OpenTelemetry core component version(s) to
1.21.0.(#5969)
See CHANGELOG for details.
1.21.0-beta.1
NuGet: OpenTelemetry.Extensions.Enrichment v1.21.0-beta.1
Breaking Change Dropped support for
net8.0andnet9.0.(#3867)
Add support for .NET 11.0.
(#3867)
Updated OpenTelemetry core component version(s) to
1.21.0.(#5969)
See CHANGELOG for details.
1.21.0-alpha.1
NuGet: OpenTelemetry.Instrumentation.EventCounters v1.21.0-alpha.1
Breaking Change Dropped support for
net8.0andnet9.0.(#3867)
Add support for .NET 11.0.
(#3867)
Updated OpenTelemetry core component version(s) to
1.21.0.(#5969)
See CHANGELOG for details.
1.20.3
NuGet: OpenTelemetry.Extensions.AWS v1.20.3
Fixed
AddXRayTraceId()andAddXRayTraceIdWithSampler()not replacingtrace IDs when targeting .NET Framework or .NET Standard. The X-Ray ID
generator now uses
Activity.TraceIdGeneratoron all target frameworks.As a result,
AWSXRayIdGenerator.ReplaceTraceId()is now public on alltarget frameworks, and
AddXRayTraceIdWithSampler()andAWSXRayIdGenerator.ReplaceTraceId(Sampler)are now obsolete on alltarget frameworks.
(#5809)
No longer throw and catch an exception in
AWSXRayPropagatorfor anX-Amzn-Trace-Idheader with upper case or padded hexadecimal identifiers,or with a trace or parent identifier of all zeros.
(#5825)
Fixed
AWSXRayPropagatorusing the value of a field of theX-Amzn-Trace-Idheader whose name only starts with
Root,ParentorSampled.(#5825)
See CHANGELOG for details.
NuGet: OpenTelemetry.Instrumentation.AWS v1.20.3
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Instrumentation.AWSLambda v1.20.3
No notable changes.
See CHANGELOG for details.
1.20.2
NuGet: OpenTelemetry.Extensions.AWS v1.20.2
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Instrumentation.AWS v1.20.2
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Instrumentation.AWSLambda v1.20.2
server.addressandserver.portnot being recorded correctly for HTTPrequests with an IPv6 address in the
Hostheader (e.g.[::1]:8080).(#5788)
See CHANGELOG for details.
1.20.2-beta.1
NuGet: OpenTelemetry.Instrumentation.Hangfire v1.20.2-beta.1
Fixed failed jobs exporting the exception message as the span status description.
The message is now only recorded when
RecordExceptionis enabled.(#5884)
Fixed baggage from a job being visible to work started by other jobs
performed on the same worker.
(#5886)
Added
EnrichWithBackgroundJobandCustomStateMappingstoHangfireMetricsInstrumentationOptions. Use them to add custom attributes tothe metrics and to count jobs in custom Hangfire states.
(#5810)
Fixed
workflow.execution.durationfor theexecutingstate. It included thetime of other measurements of this instrumentation, for example the database
query that
RecordQueueLatencyadds.(#5810)
See CHANGELOG for details.
Commits viewable in compare view.
Updated Scalar.AspNetCore from 2.18.6 to 3.0.1.
Release notes
Sourced from Scalar.AspNetCore's releases.
No release notes found for this version range.
Commits viewable in compare view.
Pinned StackExchange.Redis at 3.4.35.
Release notes
Sourced from StackExchange.Redis's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated StackExchange.Redis from 3.4.20 to 3.4.35.
Release notes
Sourced from StackExchange.Redis's releases.
No release notes found for this version range.
Commits viewable in compare view.
Pinned WolverineFx at 6.64.2.
Release notes
Sourced from WolverineFx's releases.
6.64.2
Wolverine 6.64.2 is a patch release on the 6.x maintenance line (the
6.0branch). It backports two Wolverine.HTTP fixes from 7.0 and adds no public API.Fixes
[DeduplicatedWithResponse]now works with multipart uploads and form posts. A retried upload or form post gets the first response again, where it used to get a 422. An endpoint that binds a form value is no longer refused. A form that ASP.NET Core reads before the endpoint (an antiforgery token sent as a form field) is fingerprinted too, and the antiforgery token is left out of the fingerprint, because a browser that reloads the page gets a new token for the same request. Thanks to @esond (#5563).Request.Formread. #5562 builds on this. Thanks to @uniquelau.Known 6.x behavior, unchanged: with
UseAntiforgery(), a form post with no token answers 500 rather than 400, because ASP.NET Core throws when the endpoint reads a form that failed antiforgery validation. 7.0 answers 400 through its in-endpoint antiforgery check (GH-5147), which is not backported.Full change list: #5575.
6.64.1
Wolverine 6.64.1 is a patch release on the 6.x maintenance line (the
6.0branch). It backports four bug fixes from 7.0 and adds no public API.Fixes
codegen-preview,describe-routinganddescribecommands no longer fail on an application that has a recurring schedule.6.0through #5566): MySQL node-record housekeeping no longer deadlocks.Build and CI
6.0branch, so 6.x releases are gated likemain.Microsoft.DotNet.ILCompiler. The pin conflicted with the .NET 11 SDK's runtime pack (a backport of the fix onmain).Not included: #5562 (
[DeduplicatedWithResponse]with multipart and form bodies). It depends on 7.0's async form-read rework.Full change list: #5571.
6.64.0
A small release: three fixes, one of them a new observer signal, and a JasperFx and Weasel bump. JasperFx moves from 2.100.1 to 2.102.0 and Weasel from 9.49.0 to 9.50.0; Marten (9.58.0), Polecat (5.49.0) and Fisher (1.28.0) are unchanged. There is no schema change and no breaking API change.
Fixes
NativeAckendpoint, an envelope settled before it reached a handler (an unknown message type, an unreadable payload) is released from the lease tracker and the in-memory idempotency guard. It used to stay tracked until the lease ceiling and then log a false "unsettled for 00:59:xx" warning, an hour after it was completed (GH-5443).IWolverineObserver.CircuitBreakerResetis now raised, once per trip, when a listener the breaker paused accepts messages again. Nothing ever raised it before, so an alert opened onCircuitBreakerTrippedcould never be closed by Wolverine's own signal. A new overload,CircuitBreakerReset(Endpoint, CircuitBreakerResetReason), says whether the listener came back on its own afterPauseTimeor through an explicit start or restart. Its default forwards to the existing one-argument member, so existing observers keep working unchanged (GH-5446).ResetResourceState()no longer adds a newwolverine.response.*queue on every call. Each reset had been declaring and purging every reply queue built so far, so a test suite that resets before each test slowed down with every test, and a sender started after a reset could send its replies to a queue nobody listened to, soInvokeAsync<T>()timed out (GH-5452, thanks to @alesdvorakcz).Docs
AutoCreate(#5445).What's Changed
ResetResourceState()calls by @alesdvorakcz in GH-5452: Rabbit MQ keeps one reply queue acrossResetResourceState()calls JasperFx/wolverine#5453Full Changelog: JasperFx/wolverine@V6.63.0...V6.64.0
6.63.0
This is a durability release. Most of its fixes were found by the new out-of-process durability chaos rig (
src/Testing/DurabilityChaosRig), which kills, stops, pauses and starves producers and workers, then checks a ledger for lost, duplicated and stuck messages. Dependencies are unchanged from 6.62.0 (JasperFx 2.100.1, Weasel 9.49.0, Marten 9.58.0, Polecat 5.49.0, Fisher 1.28.0). Upgrading is a package bump with no breaking API change. The one schema change is a new index on the MySQL inbox table (GH-5428), applied by the usual message storage migration.Fixes
Docs
CHAOS_*knobs and containers (GH-5409, GH-5414).What's Changed
... (truncated)
6.62.0
This is a minor release on JasperFx 2.100.1, Weasel 9.49.0, Marten 9.58.0, Polecat 5.49.0 and Fisher 1.28.0. Upgrading is a package bump: there is no schema change and no breaking API change. If your projects pin
JasperFx.Events.SourceGeneratorcentrally, pin it to the same version asJasperFx.Events(see the note at the end).New
[SagaIsResponseOnly]for an endpoint that returns a saga as its response (GH-5069).PublishOnlyToShardedPostgresqlQueues, for publishing to sharded queues with no listeners (GH-5088).AggregateExceptionof concurrency failures maps to 409 (GH-5355);[DeduplicatedWithResponse]replays ASP.NET CoreIResultresponses, and reads a replayedLocationwithout per-request reflection (GH-5381).kafka-replay --group-idoption (thanks to new contributor @Mr444-dev).WhenTrackedsees events an application commits through its own injectedIDocumentSession, on Marten, Polecat and Fisher (GH-5385, GH-5390);GenerationRules.ReuseCompiledAssemblies(JasperFx 2.100.0) is documented and tested for many hosts in one process, in Dynamic and Auto modes, the codegen command and HTTP chains (GH-5378, GH-5391).EventModelReportprints the decider line beside starts (GH-5379), andscaffoldturns a multi-event automation into one handler class (GH-5361).Fixes
DurableLocalQueue.StartAsyncskips an already accepting queue and is serialized (GH-5348).ListenerCount > 1no longer recurses forever (GH-5363).OnExceptionreturning a tuple generates code that compiles (GH-5356), andOnExceptionhandlers for the same exception type merge into one catch clause.CloudEventsMapperkeeps the envelope id on re-read, with a stable id for non-Guid CloudEvent ids (GH-5364).Applyon every stream (GH-5360, a partial fix; the rest stays open).Microsoft.DotNet.ILCompileris cleared (GH-5387).Pinning JasperFx centrally
Polecat 5.49.0 needs JasperFx 2.100.1. If
JasperFx.Eventsis lifted to 2.100.1 whileJasperFx.Events.SourceGeneratorstays pinned at 2.100.0, the generator emits nothing and projections fail at run time with "No source-generated dispatcher found". Keep the two on one version (jasperfx#1138).What's Changed
... (truncated)
6.61.0
This is a minor release. Upgrading is a package bump only: there is no schema change and no breaking API change.
New
CronSchedule.MinimumCadenceis now one second, for six-field cron expressions such as* * * * * *. Anything faster than five seconds always runs on a timer agent, andUseScheduledMessages()refuses it.SkipWhileRunning()on a recurring schedule invokes each occurrence instead of publishing it. An occurrence that comes due while the previous one is still running is skipped, and skipped occurrences are not made up later. Skips are logged and counted in the newwolverine-recurring-occurrences-skippedmetric.PauseThenCatchUpOnAllMartenDaemonActivityAsync()and the tracked-session optionPauseThenCatchUpOnAllMartenDaemonActivity()catch up the main Marten store and every ancillary store registered withIntegrateWithWolverine()in one call. A store with no events is skipped.exceptionevent (exception.type,exception.message,exception.stacktrace) on its span, instead of only the exception's type name. Exception messages can carry application data, so you can turn this off withopts.Tracking.RecordExceptionsOnSpans = false.EntityDescriptor.Ddlnow carries each EF Core entity'sCREATE TABLEscript, with its keys, foreign keys and indexes, the same wayDocumentMappingDescriptor.Ddldoes for documents. It's generated from the model, so no connection is opened, and it's the model's script rather than the database's. Non-relational providers and view-mapped entities leave it empty. Needs JasperFx 2.99.0.http.routeandhttp.request.method, the OpenTelemetry semantic convention names, alongsidehandler.type. Both are constants in the generated code. Pre-generated code should be regenerated.DeadLetterEnvelopeQuery.RangeOn(DeadLetterTimeField.SentAtorFailedAt) (#5330).FailedAtfalls back tosent_atwhenfailed_atis null, and applies to query, replay, discard and archive. The default staysSentAt. Supported by the PostgreSQL, SQL Server, MySQL, SQLite, Oracle, CosmosDb and RavenDb stores.Fixes
TrackConnectionsturned on, the handler, saga and stream tags (handler.type,message.handler,wolverine.saga.*,wolverine.stream.*) landed on themarten.connectionspan instead of the message's own span. They now stay on the message span, and on the request span for HTTP endpoints. Pre-generated code should be regenerated.ScheduleRetry(...)lost the link to the attempt that failed, because the stored envelope body wasn't rewritten when the retry was scheduled. Every message store now rewrites the body when it reschedules an envelope.DeadLetterStorageMode.NativeWithRecoverywhenEnableDeadLetterQueueRecovery()drains them, so CritterWatch's startup check no longer warns about them.EnableDeadLetterQueueRecovery(), stopping the host could throwAlreadyClosedExceptionwhen two stops ran at once, as they do underWebApplicationFactory. Stopping the dead letter queue listener is now idempotent and never throws.FindSingleTrackedMessageOfType<T>()now counts envelopes rather than distinct message values, so publishing two equal records fails the check. A message sent to several destinations still counts once. Usetracked.Sent.SingleMessage<T>()for a check per destination.PauseThenCatchUpOnMartenDaemonActivitywaits out the high water agent's current poll tick. The fix is JasperFx/jasperfx#1100.ServiceCapabilities.Sagasonce it had been handled, and the saga disappeared once every message had been. The saga report, including each store'sGetRegisteredSagasAsync, now reads the same before and after the chains compile.Balancedmode, lifting a pause on a URI that no agent owns, such as a listening endpoint, waited outAgentRestrictionConfirmationTimeoutand then threwAgentRestrictionsNotConfirmedException. It now returns at once. Agent URIs are still confirmed as before.IPolecatOutbox.EnrollorIFisherOutbox.Enrollnever flushed their outgoing messages on commit (#5309). Durable messages waited until a restart and buffered messages were lost. They now flush on commit, the same as handler sessions, and the incoming envelope is marked handled once instead of twice.Dependencies
WolverineFx.MySql. On SQL Server, aDateTimeparameter in a message store command now goes out asdatetime2instead ofdatetime. Every envelope time column isdatetimeoffset, so no column is converted either way.Thanks to @uniquelau for #5313, #5314, #5315, #5317 and #5318, and to @lahma for #5330.
Full Changelog: JasperFx/wolverine@V6.60.0...V6.61.0
6.60.0
What's Changed
Full Changelog: JasperFx/wolverine@V6.59.1...V6.60.0
6.59.1
This is a patch release with two fixes. Upgrading is a package bump only: there is no schema change and no API change.
SQL Server: the inbox and outbox seek on their indexes again
sql_variant. The statements that mark envelopes as handled, reassign them, delete them and move them to the dead letter queue all filter on the envelope id. Weasel's generic command builder has no mapping forGuid, so it bound each id asDbType.Object, which SqlClient sends assql_variant. SQL Server then had to compareCONVERT_IMPLICIT(sql_variant, [id])on every row, which rules out a seek on theuniqueidentifierprimary key. Ids are now bound asuniqueidentifier, so each statement is a primary key seek.nvarchar.received_aton the inbox anddestinationon the outbox arevarchar(250)columns, but statements that filter on them bound the address asnvarchar. Under a SQL collation such asSQL_Latin1_General_CP1_CI_AS, the default on Azure SQL, that converts the column and defeats the index. The statements affected are the per-envelope updates and deletes, inbox recovery's page load, outbox loads by destination, the scheduled message updates and the duplicate check. They now bind the address asvarchar.DateTimeparameters kept only the date. The same generic mapping typedDateTimeasDbType.Date. The message store now lets SqlClient type both values itself.sql_variantand that no plan converts an indexed envelope column. The fullSqlServerTestssuite passes (721 tests, 2 skipped).Guidassql_variant) and JasperFx/weasel#759 (DateTimeasdate). Wolverine works around both on its own, so this release doesn't wait for a Weasel release.The
runcommand no longer blocks a thread pool threadruncommand waited for shutdown by blocking a thread pool thread for the whole life of the application. That matters when a container's CPU limit is below one core.ProcessorCountis then 1, so the thread pool's minimum is one thread, and theruncommand held it. After that, every burst of work had to wait for the pool to add a thread, about 500 ms each time. The reporter saw a 200 msTask.Delayloop wake up as much as about 950 ms late on Azure Container Apps.runcommand now awaits shutdown instead of blocking. It still listens for the same three signals:ApplicationStopping, Ctrl+C, and the assembly load context unloading.AutoStartHost/WebApplicationFactorypath),RunJasperFxCommands()used to block the calling thread. It now returns a task that completes when the host shuts down.RunJasperFxCommands()orRunWolverineCommands(), whatever its persistence or transport.Full Changelog: JasperFx/wolverine@V6.59.0...V6.59.1
Commits viewable in compare view.
Updated WolverineFx.EntityFrameworkCore from 6.59.0 to 6.64.2.
Release notes
Sourced from WolverineFx.EntityFrameworkCore's releases.
6.64.2
Wolverine 6.64.2 is a patch release on the 6.x maintenance line (the
6.0branch). It backports two Wolverine.HTTP fixes from 7.0 and adds no public API.Fixes
[DeduplicatedWithResponse]now works with multipart uploads and form posts. A retried upload or form post gets the first response again, where it used to get a 422. An endpoint that binds a form value is no longer refused. A form that ASP.NET Core reads before the endpoint (an antiforgery token sent as a form field) is fingerprinted too, and the antiforgery token is left out of the fingerprint, because a browser that reloads the page gets a new token for the same request. Thanks to @esond (#5563).Request.Formread. #5562 builds on this. Thanks to @uniquelau.Known 6.x behavior, unchanged: with
UseAntiforgery(), a form post with no token answers 500 rather than 400, because ASP.NET Core throws when the endpoint reads a form that failed antiforgery validation. 7.0 answers 400 through its in-endpoint antiforgery check (GH-5147), which is not backported.Full change list: #5575.
6.64.1
Wolverine 6.64.1 is a patch release on the 6.x maintenance line (the
6.0branch). It backports four bug fixes from 7.0 and adds no public API.Fixes
codegen-preview,describe-routinganddescribecommands no longer fail on an application that has a recurring schedule.6.0through #5566): MySQL node-record housekeeping no longer deadlocks.Build and CI
6.0branch, so 6.x releases are gated likemain.Microsoft.DotNet.ILCompiler. The pin conflicted with the .NET 11 SDK's runtime pack (a backport of the fix onmain).Not included: #5562 (
[DeduplicatedWithResponse]with multipart and form bodies). It depends on 7.0's async form-read rework.Full change list: #5571.
6.64.0
A small release: three fixes, one of them a new observer signal, and a JasperFx and Weasel bump. JasperFx moves from 2.100.1 to 2.102.0 and Weasel from 9.49.0 to 9.50.0; Marten (9.58.0), Polecat (5.49.0) and Fisher (1.28.0) are unchanged. There is no schema change and no breaking API change.
Fixes
NativeAckendpoint, an envelope settled before it reached a handler (an unknown message type, an unreadable payload) is released from the lease tracker and the in-memory idempotency guard. It used to stay tracked until the lease ceiling and then log a false "unsettled for 00:59:xx" warning, an hour after it was completed (GH-5443).IWolverineObserver.CircuitBreakerResetis now raised, once per trip, when a listener the breaker paused accepts messages again. Nothing ever raised it before, so an alert opened onCircuitBreakerTrippedcould never be closed by Wolverine's own signal. A new overload,CircuitBreakerReset(Endpoint, CircuitBreakerResetReason), says whether the listener came back on its own afterPauseTimeor through an explicit start or restart. Its default forwards to the existing one-argument member, so existing observers keep working unchanged (GH-5446).ResetResourceState()no longer adds a newwolverine.response.*queue on every call. Each reset had been declaring and purging every reply queue built so far, so a test suite that resets before each test slowed down with every test, and a sender started after a reset could send its replies to a queue nobody listened to, soInvokeAsync<T>()timed out (GH-5452, thanks to @alesdvorakcz).Docs
AutoCreate(#5445).What's Changed
ResetResourceState()calls by @alesdvorakcz in GH-5452: Rabbit MQ keeps one reply queue acrossResetResourceState()calls JasperFx/wolverine#5453Full Changelog: JasperFx/wolverine@V6.63.0...V6.64.0
6.63.0
This is a durability release. Most of its fixes were found by the new out-of-process durability chaos rig (
src/Testing/DurabilityChaosRig), which kills, stops, pauses and starves producers and workers, then checks a ledger for lost, duplicated and stuck messages. Dependencies are unchanged from 6.62.0 (JasperFx 2.100.1, Weasel 9.49.0, Marten 9.58.0, Polecat 5.49.0, Fisher 1.28.0). Upgrading is a package bump with no breaking API change. The one schema change is a new index on the MySQL inbox table (GH-5428), applied by the usual message storage migration.Fixes
Docs
CHAOS_*knobs and containers (GH-5409, GH-5414).What's Changed
... (truncated)
6.62.0
This is a minor release on JasperFx 2.100.1, Weasel 9.49.0, Marten 9.58.0, Polecat 5.49.0 and Fisher 1.28.0. Upgrading is a package bump: there is no schema change and no breaking API change. If your projects pin
JasperFx.Events.SourceGeneratorcentrally, pin it to the same version asJasperFx.Events(see the note at the end).New
[SagaIsResponseOnly]for an endpoint that returns a saga as its response (GH-5069).PublishOnlyToShardedPostgresqlQueues, for publishing to sharded queues with no listeners (GH-5088).AggregateExceptionof concurrency failures maps to 409 (GH-5355);[DeduplicatedWithResponse]replays ASP.NET CoreIResultresponses, and reads a replayedLocationwithout per-request reflection (GH-5381).kafka-replay --group-idoption (thanks to new contributor @Mr444-dev).WhenTrackedsees events an application commits through its own injectedIDocumentSession, on Marten, Polecat and Fisher (GH-5385, GH-5390);GenerationRules.ReuseCompiledAssemblies(JasperFx 2.100.0) is documented and tested for many hosts in one process, in Dynamic and Auto modes, the codegen command and HTTP chains (GH-5378, GH-5391).EventModelReportprints the decider line beside starts (GH-5379), andscaffoldturns a multi-event automation into one handler class (GH-5361).Fixes
DurableLocalQueue.StartAsyncskips an already accepting queue and is serialized (GH-5348).ListenerCount > 1no longer recurses forever (GH-5363).OnExceptionreturning a tuple generates code that compiles (GH-5356), andOnExceptionhandlers for the same exception type merge into one catch clause.CloudEventsMapperkeeps the envelope id on re-read, with a stable id for non-Guid CloudEvent ids (GH-5364).Applyon every stream (GH-5360, a partial fix; the rest stays open).Microsoft.DotNet.ILCompileris cleared (GH-5387).Pinning JasperFx centrally
Polecat 5.49.0 needs JasperFx 2.100.1. If
JasperFx.Eventsis lifted to 2.100.1 whileJasperFx.Events.SourceGeneratorstays pinned at 2.100.0, the generator emits nothing and projections fail at run time with "No source-generated dispatcher found". Keep the two on one version (jasperfx#1138).What's Changed
Description has been truncated