Azure / Azure/azure-functions-host

Stopping Func Host Start

Open
#7,833 13 comments 4 reactions 0 assignees View on GitHub
Dominant language
C#
Stars
2k
Forks
482
Avg merge
2d 12h
Merged PRs (30d)
38

Description

After running ```func host start``` for debugging and testing, I press ```CTRL+C``` to terminate the session.

After upgrading to **v3.0.3904** an error message is displayed when I press ```CTRL+C```...
```
^Cinfo: Microsoft.AspNetCore.Routing.EndpointMiddleware[1]
Executed endpoint 'gRPC - /AzureFunctionsRpcMessages.FunctionRpc/EventStream'
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Request finished in 281435.3278ms 200 application/grpc
info: Microsoft.AspNetCore.Server.Kestrel[32]
Connection id "0HMCP6FGIJID5", Request id "0HMCP6FGIJID5:00000001": the application completed without reading the entire request body.
info: Grpc.AspNetCore.Server.ServerCallHandler[14]
Error reading message.
System.IO.IOException: The request stream was aborted.
---> Microsoft.AspNetCore.Connections.ConnectionAbortedException: The HTTP/2 connection faulted.
--- End of inner exception stack trace ---
at System.IO.Pipelines.PipeCompletion.ThrowLatchedException()
at System.IO.Pipelines.Pipe.GetReadResult(ReadResult& result)
at System.IO.Pipelines.Pipe.GetReadAsyncResult()
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http2.Http2MessageBody.ReadAsync(CancellationToken cancellationToken)
at Grpc.AspNetCore.Server.Internal.PipeExtensions.ReadStreamMessageAsync[T](PipeReader input, HttpContextServerCallContext serverCallContext, Func`2 deserializer, CancellationToken cancellationToken)
```
Reporting this as I'm not sure if there is an error or not

Contributor guide

Open the contributing guide

Research direction

Reproduce `func host start` on version 3.0.3904, stop it with CTRL+C, and compare the gRPC EventStream and Kestrel messages shown in the report. Trace the shutdown handling around the EventStream and determine whether the aborted request is expected; done means establishing the expected behavior and identifying a focused correction if it is not.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, grpc
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.