Shutdown quarto preview server more gracefully.

[newptcai]

Description

When I use quarto preview to start a web server to preview the document I am writing, I have to shut it down by pressing Ctrl+c. This results in the following messages being printed to the terminal:

Watching files for changes
^CTraceback (most recent call last):
  File "/home/xing/.local/bin/quarto", line 10, in <module>
    sys.exit(run())
             ^^^^^
  File "/home/xing/.local/share/uv/tools/quarto-cli/lib/python3.11/site-packages/quarto_cli/quarto.py", line 7, in run
    return sp.call([command] + sys.argv[1:])
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/xing/.local/share/uv/python/cpython-3.11.11-linux-x86_64-gnu/lib/python3.11/subprocess.py", line 391, in call
    return p.wait(timeout=timeout)
           ^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/xing/.local/share/uv/python/cpython-3.11.11-linux-x86_64-gnu/lib/python3.11/subprocess.py", line 1264, in wait
    return self._wait(timeout=timeout)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/xing/.local/share/uv/python/cpython-3.11.11-linux-x86_64-gnu/lib/python3.11/subprocess.py", line 2053, in _wait
    (pid, sts) = self._try_wait(0)
                 ^^^^^^^^^^^^^^^^^
  File "/home/xing/.local/share/uv/python/cpython-3.11.11-linux-x86_64-gnu/lib/python3.11/subprocess.py", line 2011, in _try_wait
    (pid, sts) = os.waitpid(self.pid, wait_flags)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
KeyboardInterrupt

I think Quarto could probably hide these warnings.

[mcanouil]

@it22318466 thanks, but taking the time to properly format your pasted LLM output would be appreciated before posting it.

Also do note that providing unverified LLM output is against the Code of Conduct, so before to fully proofread the content you decide to post from your LLM.

As clearly you did not review the content you posted or even Quarto CLI codebase, I'm hiding it.

[newptcai]

While I understand the dislike of LLM generated content, I feel it's probably more productive to address the underline issue. This one really should be 2 minutes LLM coding fixable.

[mcanouil]

While I understand the dislike of LLM generated content, I feel it's probably more productive to address the underline issue.

The concern here is not with LLM-generated content as such, but with pasting content that is incorrect and was not verified before submission.

This one really should be 2 minutes LLM coding fixable.

Comments like this are not particularly productive or helpful to the team.
Quarto is maintained by a small team managing nearly two thousand open issues, and the focus right now is on Quarto 2 (in addition to Quarto 1), which addresses a much broader set of problems and unlocks features that cannot be delivered incrementally.
LLMs are not a reliable shortcut for ensuring a fix is correct, complete, and consistent across platforms.
If this feels straightforward to you, a pull request would be very welcome, including tests and cross-platform verification.
The contributions that move things forward most are those that come with a solution, not just a request.
Thanks for your continued interest in the project.

[newptcai]

That is a fair point. I will try to fix this myself and test it on Linux and Windows.

But I do hope the team will have time for reviewing the (possibly very simple) pull request.

[cderv]

Thanks for the report.

It took me some time to understand that this is specific to Quarto installed via the Python package (pip install quarto-cli / uv tool install quarto-cli).

The traceback comes from the Python wrapper — the run() function in https://github.com/quarto-dev/quarto-cli-pypi doesn't catch KeyboardInterrupt, so pressing Ctrl+C surfaces as an unhandled exception instead of a clean exit.

The fix is straightforward: catch KeyboardInterrupt in the entry point and exit with code 130 (the conventional exit code for Ctrl+C). We'll get a fix into https://github.com/quarto-dev/quarto-cli-pypi.

[cderv]

PR at

• fix: exit cleanly on Ctrl+C quarto-cli-pypi#7

This will be fixed at next release.