Jonas Nyrup

To be frank, every [change in behavior](https://www.hyrumslaw.com/) breaks someone's [workflow](https://xkcd.com/1172/). But I do think you're right that what you're seeing is an _unintentional_ change of what we _fixed_ with #2614....

Thanks for the quick reply and acknowledgement. Here's the fuzzer campaign I created to fuzz MemoryPack [MemoryPackFuzzing.zip](https://github.com/user-attachments/files/16190202/MemoryPackFuzzing.zip)

...And to also exercise the serialization paths, we can update the fuzzer to incorporate round-trip fuzzing similar to what is also done in https://github.com/Cysharp/MemoryPack/blob/main/tests/MemoryPack.Tests/Fuzz.cs. ```cs try { var serialized =...

> As a potential compromise in the case of infinite collections, it could maybe list up to some max number of items? Did you see this suggestion @dennisdoomen It shouldn't...

I agree on the requirements. On the second parts my gut feeling is to pick at most 10. How many items were there in the collection in your test suite?

It it was me I would just raise the current `Take(1)` to e.g. `Take(10)`, adjust the tests, add release notes and call it a day. ... If my test started...

Great to hear. I'd like to give this a shot 🤞 I got it working for `DerivedTypeSwitchMapping` in https://github.com/jnyrup/mapperly/tree/issue1827. It clearly needs a lot of cleanup. I'll try to study...

I won't have time any time soon to make progress on this. So if anyone wants to take over, just go ahead.

This has been changed for: * `Fare` in #1423 -- released with https://www.nuget.org/packages/AutoFixture/5.0.0-preview0006 * `System.ComponentModel.Annotations` in #1429 -- released with https://www.nuget.org/packages/AutoFixture/5.0.0-preview0007 As I read https://github.com/AutoFixture/AutoFixture/issues/1356#issuecomment-1342819426 it won't be backported to...

It might be related to #12274 I experienced the same error when building a C# projects in a pipeline using a Visual Studio instead of plain `dotnet build`. The machine...