Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[Bug] Infinite loop when just running sift with no input #37

@GCrispino

Description

@GCrispino

Describe the bug
If you just run sift with no input, it hangs on the "Compiling" and/or "Waiting for test results..." stages, even if I press Ctrl+C in the terminal.

It appears that if I press Ctrl+C, it goes from the "Compiling" stage to the "Waiting for test results..." one, but doesn't go anywhere from that.

To Reproduce
Just run sift, with no piped input:

> sift

Expected behavior
The program should either not run or allow me to exit somehow, even if just by pressing CTRL+C.

Screenshots
This is a screen recording that should illustrate the behaviour:

Gravacao.de.Tela.2025-11-09.as.17.34.54.mov

Versions:

  • Go Version: 1.25.0
  • CLI Version: 0.12.1

Additional context
I'm running MacOS, and would be open to open a PR to handle SIGINT in the code.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions