Rob Harwood

Thanks @Greg-Hitchon - I hadn't noticed this had been reported before. This is probably the most urgent issue at the moment as it's a security issue when response outputs bleed...

Hi @xuzhg, I've tried this with both `8.0.0-beta` and `8.0.0-Nightly202103051314` (the last nightly prior to the routing attribute changes). Both still fail the test, so unfortunately this doesn't appear fixed,...

I've been doing some more digging; there is something fishy going on in `ODataResourceSerSerializer.cs` when it calls `messageWriter.CreateODataResourceSetWriterAsync`. The writer returned from this method can seemingly come back with a...

Ok, it looks like part of the process used for creating a writer in the OData library gets an instance of `ODataMessageInfo` from the DI container. This is an implementation...

Ok, interestingly it seems as though for batched requests a DI scope is created per logical request, but for non-batched requests the root DI container for the EDM type is...

Hi, I've had a stab at a PR to fix this - #111 I've added the per-request scoping as a middleware. This means that when using OData you will always...

@xuzhg - thanks for the reply! I thought of making the change in the place you suggested instead of an `app.UseOData()` call, but there were two things that stopped me;...

Hi @xuzhg, any thoughts on my points above? I'm looking to test this change next week. thanks

Hi @xuzhg, Great stuff on the RC thank you! The issue in b65d7e9 isn't the root cause, I had identified and fixed that one in my PR (and mentioned it...

Hi, yes we have the same issue as of 16.5.1 and still see it on 16.5.2. Error is; Missing class: android.arch.paging.PositionalDataSource Something has definitely broken, am happy to downgrade to...