Incorrect timeout message when timeout set to 60s or more #96

New Issue

fergalmoran · 2025-08-09T17:14:59Z

fergalmoran commented

2025-08-09 17:14:59 +00:00

Originally created by @martinstenhoff on 4/18/2018

If you configure a StartupTimeout of 60 seconds or more (e.g. using spa.Options.StartupTimeout = TimeSpan.FromSeconds(60); in app.UseSpa) and the timeout triggers you get the following slightly confusing message:

The Angular CLI process did not start listening for requests within the timeout period of 0 seconds. Check the log output for error information.

This is due to the timeout messages using TimeSpan.Seconds instead of TimeSpan.TotalSeconds.

*Originally created by @martinstenhoff on 4/18/2018* If you configure a StartupTimeout of 60 seconds or more (e.g. using `spa.Options.StartupTimeout = TimeSpan.FromSeconds(60);` in app.UseSpa) and the timeout triggers you get the following slightly confusing message: _The Angular CLI process did not start listening for requests within the timeout period of 0 seconds. Check the log output for error information._ This is due to the timeout messages using TimeSpan.Seconds instead of TimeSpan.TotalSeconds.

fergalmoran closed this issue

2025-08-09 17:14:59 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/JavaScriptServices#96