shoguns6
shoguns6
> This is consistently happening to us in production also. We are calling flush from two places and in some scenarios that seems to cause the deadlock (it may be...
Facing the same problem in .NET Core 3.1 and OData 7.3.0
> Seeing the same problem here in .NET Core 3.1 and OData 7.3.0 Me too!!
> @KanishManuja-MS Is there a way to handle this? > I'm facing the same issue! > Does anyone know a way to handle this exception? One way it worked for...
in the controller get method.... use OdataQueryOptions explicitly... like the one below.. or u can catch that error in middleware. Supporting ODataQueryOptions in existing Web API | | | |...