You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
realize your terminal has hung, and ctrl-c is unavailable
How often does it reproduce? Is there a required condition?
always. i'd assume this is the REPL trying to generate a completion and in turn executing the loop
What is the expected behavior? Why is that the expected behavior?
perhaps the completer should be killed after a certain period? i've encountered similar issues when trying to use the node CLI to query large JSON datasets, but those all finish in finite time. i'm not sure if it would be possible, given how the event loop works, but the preferable behavior would be to have the completer be interrupted on any keypress.
What do you see instead?
see above
Additional information
No response
The text was updated successfully, but these errors were encountered:
Version
v22.4.1
Platform
Subsystem
No response
What steps will reproduce the bug?
node
REPLwhile (true) {}
, without pressing enterHow often does it reproduce? Is there a required condition?
always. i'd assume this is the REPL trying to generate a completion and in turn executing the loop
What is the expected behavior? Why is that the expected behavior?
perhaps the completer should be killed after a certain period? i've encountered similar issues when trying to use the node CLI to query large JSON datasets, but those all finish in finite time. i'm not sure if it would be possible, given how the event loop works, but the preferable behavior would be to have the completer be interrupted on any keypress.
What do you see instead?
see above
Additional information
No response
The text was updated successfully, but these errors were encountered: