quarto-dev / quarto-dev/quarto-cli
Quarto does not remember authentication on Linux
@cscheid is already working on this.
Since Oct 22, 2024.
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 458
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 41
Description
Bug description
Whenever I want to publish a new document to Netlify on Linux, the quarto publish command always prompts me to authenticate on the Netlify website. On macOS (and presumably on Windows), authentication has to be done only once, so I assume that this should be the intended behavior. I didn't try any other providers.
Steps to reproduce
Run quarto publish netlify test.qmd always results in the authorize prompt. Even if I select Y, authorize, and publish the document successfully, I get prompted the next time I try to publish (which includes just updating an existing document).
Expected behavior
Authorization should be required only once.
Actual behavior
Authorization is required on every publish.
Your environment
- OS: Arch Linux
- Browser: Google Chrome
Quarto check output
Quarto 1.4.555
[✓] Checking versions of quarto binary dependencies...
Pandoc version 3.1.11: OK
Dart Sass version 1.69.5: OK
Deno version 1.37.2: OK
[✓] Checking versions of quarto dependencies......OK
[✓] Checking Quarto installation......OK
Version: 1.4.555
Path: /opt/quarto/bin
[✓] Checking tools....................OK
TinyTeX: (not installed)
Chromium: (not installed)
[✓] Checking LaTeX....................OK
Using: Installation From Path
Path: /usr/bin
Version: undefined
[✓] Checking basic markdown render....OK
[✓] Checking Python 3 installation....OK
Version: 3.10.14
Path: /home/clemens/.pyenv/versions/psychopy/bin/python3
Jupyter: (None)
Jupyter is not available in this Python installation.
Install with python3 -m pip install jupyter
[✓] Checking R installation...........OK
Version: 4.4.0
Path: /usr/lib64/R
LibPaths:
- /home/clemens/.R/4.4
- /usr/lib/R/library
knitr: 1.46
rmarkdown: 2.26
[✓] Checking Knitr engine render......OK
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.