Azure / Azure/azure-functions-host
Emit warning if signs of bad async patterns are detected in out-of-proc languages
Open
area: out-of-proc
- Dominant language
- C#
- Stars
- 2k
- Forks
- 482
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 38
Description
We know there's a bad async pattern somewhere when there are calls to log on a given function invocation that has already completed.
Similar to https://github.com/Azure/azure-functions-nodejs-worker/issues/154, but on the functions host to capture this for all out of proc languages.
Contributor guide
Research direction
No file, test, or entry point is named. Start by reviewing the functions host's invocation and logging lifecycle, then compare the related azure-functions-nodejs-worker issue; done means detecting logs after an invocation completes and emitting a warning for supported out-of-proc languages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp
- Domain
- backend, cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100