Sporadic C# compilation issue
See original GitHub issueOver the past few days, a few function apps have run into a compilation failure that seems to be caused by an attempt to queue additional Roslyn compilation events after the compilation is marked as completed, leading to an InvalidOperationException
with the message: Cannot enqueue data after PromiseNotToEnqueue.
Opening this for investigation and tracking.
Issue Analytics
- State:
- Created 7 years ago
- Comments:41 (22 by maintainers)
Top Results From Across the Web
Compiler randomly throwing different errors
They happen in different files and there are no obvious syntax errors there. I'm using Windows 7, Eclipse with the C/C++ plugin to...
Read more >[SOLVED]Random errors while compiling C++ code / ...
I have random errors when compiling software. It is not related to the software source code. Everytime an error occurs, I can just...
Read more >[package] diligent-core/2.5.1: sporadic compilation error
Package Name/Version: diligent-core/2.5.1 · Operating System+version: Linux Ubuntu 20.04 · Compiler+version: GCC 11.2 · Conan version: conan 1.43.2 ...
Read more >Compilation error
Compilation error or compile error refers to a state when a compiler fails to compile a piece of computer program source code, either...
Read more >Unable to resolve configuration with compiler path ERROR ...
Hi everyone. I just started using Platformio and I am actually loving it. And today suddenly I started getting this problem first I...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This issue still exists!
We’ve reached out to the compiler team as we were still seeing instances of this happening. We’ve put some mitigation steps that help some scenarios, but as you found, we’re not as aggressive with those steps. We did get an update from the team and there’s a fix in the latest compiler version. We’ll be deploying that with our next release.