You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we found a strange behavior when AggregateBuilder() is null for single stream aggregates that do not have neither public constructor nor Create() method and when stream is aggregated in multiple parallel calls:
open it in IDE and navigate to Sample\Helpdesk\Helpdesk.Api project
run from that directory
docker compose up -d postgres
dotnet run -- codegen write
place a breakpoint in program.cs in a catch block (i.e. line 164)
debug AggregateStreamInParallelOf test
you should land with exception in SingleStreamProjectionLiveAggregationXXXXXX like on my very first screenshot.
i'm wondering if it is a valid use case or we're doing something completely stupid that we get such an error (i.e. i had to disable optimistic check in order to reproduce it)
I'm actually ready to contribute if you decide that this should be corrected and point me a bit into the places that i should look at..
Thanks!
The text was updated successfully, but these errors were encountered:
Dear Community,
we found a strange behavior when
AggregateBuilder()
is null for single stream aggregates that do not have neitherpublic constructor
norCreate()
method and when stream is aggregated in multiple parallel calls:the aggregate:
I forked your example repository and made some changes in Helpdesk sample.
a-shtifanov-laya/marten-concurrency-bug@39b8ca0
In order to reproduce this behavior:
Sample\Helpdesk\Helpdesk.Api
projectdocker compose up -d postgres
dotnet run -- codegen write
AggregateStreamInParallelOf
testyou should land with exception in
SingleStreamProjectionLiveAggregationXXXXXX
like on my very first screenshot.i'm wondering if it is a valid use case or we're doing something completely stupid that we get such an error (i.e. i had to disable optimistic check in order to reproduce it)
I'm actually ready to contribute if you decide that this should be corrected and point me a bit into the places that i should look at..
Thanks!
The text was updated successfully, but these errors were encountered: