Skip to content

Core tools not responding to ctrl-C #4355

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mattchenderson opened this issue Apr 8, 2025 · 1 comment
Open

Core tools not responding to ctrl-C #4355

mattchenderson opened this issue Apr 8, 2025 · 1 comment

Comments

@mattchenderson
Copy link
Contributor

Version

4.0.6821 on Windows (and 4.0.6610 on Mac)

Description

The core tools doesn't seem to be responding properly to terminate commands anymore. Observed both on Windows and Mac. Instead, it just hangs.

This might be a duplicate of #4268, but the attempted connection to Azurite is not present in my repros.

I don't know if other environment factors are present that would influence this, but seeing it across users and OSes makes me think there is something surprising at play.

Steps to reproduce

Func start -> Ctrl+C

@paulyuk
Copy link
Member

paulyuk commented Apr 10, 2025

+1, I see this even on most basic HTTP example. I observe this error after waiting some time (30s?)

^C[2025-04-10T18:02:13.733Z] Host did not shutdown within its allotted time.
[2025-04-10T18:02:13.749Z] The Azure Storage connection string is either empty or invalid. Unable to record diagnostic events, so the diagnostic logging service is being stopped.
[2025-04-10T18:02:13.749Z] Azure.Data.Tables: Value cannot be null. (Parameter 'connectionString').
[2025-04-10T18:02:13.749Z] Unable to get table reference. Aborting write operation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants