TestCafe waits for timeout and debug when you trigger restart from CLI with Ctrl+R

[Klaster1]

What is your Scenario?

1. Have a test with a long timeout that fails (like, 60s) or a t.debug that locks the page.
2. Run the test in live mode so it pauses on either of these.
3. In CLI, press Ctrl+R to restart the test.

What is the Current behavior?

TestCafe waits for debug to unlock (never happens, you have to manually do that) or for timeout to stop.

What is the Expected behavior?

TestCafe ignores timeouts or debugs and restarts the test immediately.

TestCafe version

3.7.2

This happens to me very often when I debug issues I find during tests, be it app bugs (t.debug helps with these) or issues in my test code (waiting with a generous 60s timeout for assets to load and parse, but encountering an issue at that line of test - maybe you asserted the wrong thing). It's a huge UX issue and a big source of annoyance. Why would I even want to wait for these if I triggered a test restart?

[github-actions[bot]]

We appreciate you taking the time to share information about this issue. We reproduced the bug and added this ticket to our internal task queue. We'll update this thread once we have news.