quarto-dev / quarto-dev/quarto

Quarto installation not found when rendering .qmd in VScode on Ubuntu 22.0

Open
#362 15 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug vscode
Dominant language
TypeScript
Stars
645
Forks
62
Avg merge
17h 42m
Merged PRs (30d)
13

Description

Bug description

The issue is similar to quarto-dev/quarto-cli#5572 (or quarto-dev/quarto-cli#1882): I installed the quarto CLI in a conda environment, which works fine for interactive use and in the VSCode terminal, but which somehow isn't properly detected by the quarto extension when trying to render a doc.

Steps to reproduce

Create the virtual environment with conda env create -f environment.yml, where environment.yml contains the following:

name: intro_to_python
channels:
  - conda-forge
dependencies:
  - python=3.12
  - pylint
  - yapf
  - build
  - jedi
  - unidecode
  - wheel
  - isort
  - ca-certificates
  - openssl
  - numpy
  - scipy
  - matplotlib
  - pandas
  - scikit-learn
  - seaborn
  - ipython
  - jupyter
  - certifi
  - quarto
  - perl

Then activate the created environment and verify that everything works with quarto:

conda activate intro_to_python
quarto check

Use a local .vscode/settings.json at the root of my workspace:

{
  "quarto.path": "path/to/your/envs/intro_to_python/bin/quarto",
}

image
/

Expected behavior

I expected the quarto VSCode extension to properly pick-up my quarto CLI install.

Actual behavior

The quarto VSCode extension does not detect my quarto CL install. Note that the same happens if I set "quarto.path" in the User's settings.json instead of the local one.

image

Your environment

VSCode on Ubuntu 22.0

Quarto check output
[✓] Checking versions of quarto binary dependencies...
      Pandoc version 3.1.1: OK
      Dart Sass version 1.58.3: OK
[✓] Checking versions of quarto dependencies......OK
[✓] Checking Quarto installation......OK
      Version: 1.3.450
      Path: /home/tvatter/mambaforge/envs/intro_to_python/bin

[✓] Checking basic markdown render....OK

[✓] Checking Python 3 installation....OK
      Version: 3.12.1 (Conda)
      Path: /home/tvatter/mambaforge/envs/intro_to_python/bin/python
      Jupyter: 5.7.1
      Kernels: python3

(/) Checking Jupyter engine render....0.00s - Debugger warning: It seems that frozen modules are being used, which may
0.00s - make the debugger miss breakpoints. Please pass -Xfrozen_modules=off
0.00s - to python to disable frozen modules.
0.00s - Note: Debugging will proceed. Set PYDEVD_DISABLE_FILE_VALIDATION=1 to disable this validation.
0.00s - Debugger warning: It seems that frozen modules are being used, which may
0.00s - make the debugger miss breakpoints. Please pass -Xfrozen_modules=off
0.00s - to python to disable frozen modules.
0.00s - Note: Debugging will proceed. Set PYDEVD_DISABLE_FILE_VALIDATION=1 to disable this validation.
[✓] Checking Jupyter engine render....OK

(\) Checking R installation...........Warning message:
D-Bus service not found!

- If you are in a container environment, please consider adding the
  following to your configuration to silence this warning:

  options(bspm.sudo = TRUE)

- If you are in a desktop/server environment, please remove any 'bspm'
  installation from the user library and force a new system
  installation as follows:

  $ sudo Rscript --vanilla -e 'install.packages("bspm", repos="https://cran.r-project.org")' 
[✓] Checking R installation...........OK
      Version: 4.3.2
      Path: /usr/lib/R
      LibPaths:
        - /home/tvatter/R/x86_64-pc-linux-gnu-library/4.3
        - /usr/local/lib/R/site-library
        - /usr/lib/R/site-library
        - /usr/lib/R/library
      knitr: 1.45
      rmarkdown: 2.25

[✓] Checking Knitr engine render......OK

Contributor guide

No contributing guide indexed for this repository

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

Reproduce the setup from environment.yml on Ubuntu, activate the conda environment, run quarto check, and inspect the VSCode extension's handling of the quarto.path setting in .vscode/settings.json. Done means the extension detects the installed CLI and renders the .qmd document successfully with that configuration.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, typescript, vscode
Domain
devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.