LGTM.com - false positive "Statement has no effect" for Python await

[maxfischer2781]

Description of the false positive

The await expression is used to run coroutines, which by design have side-effects. However, CodeQL erroneously treats a bare await expression like any other bare expression and thus assumes it has no side-effects and is used in error. This leads to false-positive flags when await is used to trigger a side-effect without a return value.

def foo():
    ...
    # close a critical resource
    await aclose

URL to the alert on the project page on LGTM.com GithHub

https://github.com/maxfischer2781/asyncstdlib/security/code-scanning/9

[Dreamsorcerer]

This is a pretty frequent false positive. Can we just disable this rule on all awaits?

[Dreamsorcerer]

Ugh, I'm running through the remaining open issues on our repository, and when I say pretty frequent, I mean there are literally atleast 100-150 alerts on our codebase that I need to reject as false positives...