Serious GraphMerger bug with 7.0.2

[michaelcsikos]

It looked like the GraphMerger problems had been resolved, but since Friday I have been trying to work this one out. I have managed to strip down an example to just two tests, one which shows the expected result using just SaveAsync(), and the failure with SaveAndMergeAsync(). The only difference between the two tests is how the save is performed:

if (merge)
    await instance.SaveAndMergeAsync();
else
    instance = await instance.SaveAsync();

GraphMergerTest.zip

Open the Test Explorer and run WidgetTests. UpdateWithMergeWidgetTest will fail, and UpdateWithoutMergeWidgetTest should pass.

In the Standard Output, you'll see that one of the child items has been incorrectly merged in, there is a duplicate Guid, and one of them has been lost. It is usually the last item which is a duplicate of the second.

This is a show stopper for us currently. I could roll back to 6.2.2, but this would require a fair bit of reworking as the Blazor view model methods changed in 7.0.0. I would really appreciate someone looking into this.

[rockfordlhotka]

Adding a reference to the PR that (theoretically) fixed this issue:

#3481

[rockfordlhotka]

fyi, I'm in Prague this week speaking at a conference and otherwise on holiday, so it won't be until sometime next week when I am likely to get a chance to look into this.

@russblair might have an idea, as he dug into the #3481 issue in depth.

[russblair]

I will try to take a look at this later today or tomorrow.

[russblair]

As far as we can tell, the bug is not in the GraphMerge logic but is in the DataPortal logic. The bug is identified after the FetchAsync in the Fetch method on line 118 of the SimpleDataPortal.cs. The obj.Instance identity manager has the incorrect next identity value. We are unclear as to how this is happening or how to narrow it down further.

[michaelcsikos]

DoesSaveAndMergeAsync end up calling Fetch?

[rockfordlhotka]

It does not call Fetch. It calls Update, gets the result, and merges the result with the original graph.

[russblair]

We think we have a working solution. Check it out at https://github.com/russblair/csla/tree/RB/v7.0.3_IdentityManagerIssue%233581.

[russblair]

I did not raise a PR because we have added Michael's test code to the project and I wanted to make sure that was ok with both of you (Micael and Rocky) first.

[michaelcsikos]

That's fine. I have never written a test like this before and have been developing with CSLA for 16 years. I was pleased to discover it was reproducible in a test and not just in Blazor.

[rockfordlhotka]

More tests are good!!

[rockfordlhotka]

@russblair can you create a PR against main as well so this fix gets into CSLA 8 and future versions?

[russblair]

Yes. I can do that Regards, Russ From: Rockford Lhotka ***@***.***> Sent: Thursday, November 30, 2023 4:34 PM To: MarimerLLC/csla ***@***.***> Cc: Russ Blair ***@***.***>; Mention ***@***.***> Subject: Re: [MarimerLLC/csla] Serious GraphMerger bug with 7.0.2 (Issue #3581) @russblair <https://github.com/russblair> can you create a PR against main as well so this fix gets into CSLA 8 and future versions? — Reply to this email directly, view it on GitHub <#3581 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADCXB7AWQLMYTIMAR3LX2BDYHD3T3AVCNFSM6AAAAAA7SZQPS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZUGU4TINZWGE> . You are receiving this because you were mentioned. <https://github.com/notifications/beacon/ADCXB7CVMWZN4T4W4CG3EX3YHD3T3A5CNFSM6AAAAAA7SZQPS2WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTNLGY4S.gif> Message ID: ***@***.*** ***@***.***> >

[rockfordlhotka]

@michaelcsikos and @russblair I have pushed a prerelease of 7.0.3 to nuget, so if you can try that version to ensure it fixed the issue I think we'll be all set.

[michaelcsikos]

The 7.0.3 prerelease looks good.