Open kf6kjg opened 3 years ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Lol. Last I checked it's still a bug.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Yep. No actions. Not heard a peep. But do a problem.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Go away stale bot.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I said go away bot. :P
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
π Bug Report
The CLI logger is not exiting when the pipe closes. This leaves surrounding systems, such as PM2 or Azure WebApp, thinking the service is running when it has long since left the building.
To Reproduce
Steps to reproduce the behavior:
Alternatively with a simulated crash:
Observe that the logger doesn't return the prompt to the user unless terminated via signal - aka CTRL-C.
Of course a real application could be producing many more logs before exiting.
Expected behavior
The logger to send the log object to the Azure Insights service and then exit.
Your Environment
node:14-alpine3.11
Docker image.The REDACTED value in the above comes from the Application Insights Instrumentation Key line, the location of which on the Azure Portal interface is highlighted in green here: