Arthur Stankevich
Arthur Stankevich
We just faced a similar problem in our application, but the impact was much worse. As in the first post in this thread, the first query was implicitly executed, returned...
@sdanyliv I've created a repo where the issue is reproduced https://github.com/a-stankevich/LinqKit_Issue59/blob/main/LinqKit_Issue59/Program.cs. Thank you for help!
Thank you for detailed explanation @sdanyliv. I understand the situation we discuss is caused by incorrect usage of `AsExpandable()`. You say that such statement will fail, and actually it would...
I actually forked this repo to apply fix from that SO thread only to find that it's actually already fixed and works fine. It doesn't work in OPs scenario because...
https://github.com/angelobreuer/localtunnel.net/blob/feat/server/src/Localtunnel.Server/TunnelInformation.cs#L72 this needs to include querystring
This is fixed now, thank you!
Fixed by removing line with `DotNetCliToolReference` from csproj file.
Workaround is to use version 1.4 instead of the latest 1.5
Found it here: https://github.com/borisbanushev/stockpredictionai/tree/f1984b952b86d61653758ddcd0dc6dd3735a5e5b upd: not quite it
This issue is also important for us, as we use LINQKit extensively in our project and there are a lot of shared methods returning expandable queries. Combining those queries in...