Task stop executing after block with Dapper async call

If task {} have certain depth it silently stop executing after let! block that contains Dapper async call.

This is connected to Dapper library, but because I think this behavior should never happen, regardless of code inside task, I am raising issue here.

Repro code here: https://github.com/jindraivanek/task-bug-repro

Repro steps

Provide the steps required to reproduce the problem:

1. Checkout repro: https://github.com/jindraivanek/task-bug-repro
2. Start MSSQL server by docker commands, or change connection string to your local MSSQL server
3. Run project, program will not end, task complexTask will never finish, second let! bock is never executed.

Expected behavior

Task should never silently stop executing.

Actual behavior

Task stop executing after first let! block with Dapper async call. (But not during or after Dapper call, all code in this block is executed.)

Known workarounds

• use synchronous variant of Dapper method
• refactor to have less depth of task
• use async instead of task All these workaround are showcased in repro code.

Related information

Reproduced with MSSQL, does not reproduce with SQLite, didn’t test on another databases.

• Operating system Windows 10
• .NET Runtime kind (.NET Core, .NET Framework, Mono) .NET 7
• Editing Tools (e.g. Visual Studio Version, Visual Studio) not important, but Rider

[jindraivanek]

@jindraivanek have you tested it with TaskBuilder, Ply or IcedTasks? Wondering if it works there.

@vzarytovskii Didn’t test it, I can try it later today.

[vzarytovskii]

Oh, ok, I will close it, but I still want to understand why it’s not statically compilable.