func start on Linux won't stop upon recieving SIGTERM
#3074
Labels
Comments
ghost
added
the
|
Is there any update on this issue? We are getting this issue as well in our build pipelines when trying to run integration tests |
|
We don't have anything yet. I tried looking through the source myself to figure something out but I'm not a C# guy. |
5 tasks
|
Just stumbled upon this same issue and opened a PR, at least for the version published on npm. |
|
Has anyone had time to look a this yet? I need this fix... |
|
Same problem exists on MacOS. |
|
Would be nice if this could get some attention. |
|
Link #3222 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If I execute
func starton Linux and then send a termination request (kill -s SIGTERM <pid>), the local runner will ignore the request.Sending a termination signal like this should result in the program closing. Instead, the process stays open indefinitely.
Interestingly, SIGINT works just fine.
I'm running Linux and I've tested this with both a Node project and a Java project.
This is currently preventing the Azure Functions Gradle Plugin from shutting down down the
azureFunctionsRuntask correctly, which is a huge usability problem for that plugin. However, the root issue remains infunc start.The text was updated successfully, but these errors were encountered: