quarto-dev / quarto-dev/quarto-cli

Pressing ctrl-c when quarto is updating breaks installation

Open
#440 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

builds enhancement
Dominant language
JavaScript
Stars
6k
Forks
458
Avg merge
1d 9h
Merged PRs (30d)
41

Description

I installed Quarto by cloning this repo and running ./configure-macos.sh. Sometimes I update with a git pull, and then when I actually use quarto, it updates Deno. If I press ctrl-c when it's in the middle of updating, it breaks my quarto installation. For example:

$ quarto render
Bootstrapping Deno...
~/nobackup/quarto-cli/package ~/nobackup/quarto-cli
~/nobackup/quarto-cli/package/dist ~/nobackup/quarto-cli/package ~/nobackup/quarto-cli
~/nobackup/quarto-cli/package/dist/bin ~/nobackup/quarto-cli/package/dist ~/nobackup/quarto-cli/package ~/nobackup/quarto-cli
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   667  100   667    0     0   2533      0 --:--:-- --:--:-- --:--:--  2605
 46 28.7M   46 13.3M    0     0  5045k      0  0:00:05  0:00:02  0:00:03 6572k^C

$ quarto render
-bash: /usr/local/bin/quarto: No such file or directory

Running ./configure-macos.sh fixes it, but it would be nice if it didn't break in the first place.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading configure-macos.sh and tracing the update/bootstrap path used when quarto render updates Deno. Reproduce the interrupted update if possible, then verify that pressing Ctrl-C does not leave the quarto command unavailable and that a subsequent render still works.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, shell
Domain
build-system, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.