Bruce Bowyer-Smyth
Bruce Bowyer-Smyth
Not sure if related but we had the same symptoms if VS was running "As administrator". Running VS normally or running the app exe directly worked fine.
Test code ``` public class ParseQuery { NpgsqlCommand _cmdLinq = default!; NpgsqlCommand _cmdSelect = default!; [GlobalSetup] public void Setup() { _cmdLinq = new NpgsqlCommand(@"SELECT ""Extent1"".""MultiframeModuleId"", ""Extent1"".""FrameIncrementPointer"", ""Extent1"".""PageNumberVector"" FROM ""public"".""MultiframeModule"" AS...
No worries. Can remove changes just let me know.
@robinrodricks Yes stream and other places in system will now prefer to use the new overloads if they don't already have an array. For example `FileStream.CopyToAsync` uses the memory overload...
Added 2 more UploadDownload tests as the existing ones weren't using the streams directly. Fixed a couple of compiler warnings in the file also.
I've put up a draft PR but I need to sort out a machine I can run the docker tests on
@NinoFloris Another alternative to #5985, what do you think about this approach? #6016 could then be moved to the new class as well.
@NinoFloris is this a change you would be interested in? I know there is some desire for small AOT size.
`Encoding.UTF8` uses the "replace invalid chars" option whereas the main Npgsql encoding uses the "throw on invalid" setting. I tried to combine the converter but most things were a regression...