-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when using async queries involving result operators and projecting a collection (N+1 queries scenario) #6534
Comments
Thanks @maumar. Moved. |
Problem was that during result operator processing, when creating expression for GetResult involving InjectParameter call we were not propagating CancellationToken. Fix is to call a helper method that takes care of that, rather than Expression.Call.
Problem was that during result operator processing, when creating expression for GetResult involving InjectParameter call we were not propagating CancellationToken. Fix is to call a helper method that takes care of that, rather than Expression.Call.
Fixed in fba433e |
@maumar Is the fix for this issue checked in the 1.1.1 branch? Should the issue be reopened for approval? |
This patch bug is approved. Please use the normal code review process w/ a PR and make sure the fix is in the correct branch, then close the bug and mark it as done. |
Is there any indication when the 1.1.1 release will go public? Alternatively, is there a workaround for this? |
@RehanSaeed it's about 2 - 3 weeks out. We're working on setting up a MyGet feed so people can try out the patch fixes. |
Steps to reproduce
I have method named
GetSeriesData
:I call
GetSeriesData
method:The issue
Calling
SingleOrDefaultAsync
throws exceptionBut if i call
SingleOrDefault
instead ofSingleOrDefaultAsync
all works fineAlso this code works with EF6
The text was updated successfully, but these errors were encountered: