quarto-dev / quarto-dev/quarto-cli

Julia kernel is not found anymore from 1.3 to 1.4 update when available through Conda.jl

Open
#8,573 8 comments 0 reactions 1 assignee View on GitHub

@cderv is already working on this.

Since Feb 2, 2024.

bug engines-julia engines-jupyter
Dominant language
JavaScript
Stars
6k
Forks
458
Avg merge
1d 9h
Merged PRs (30d)
41

Description

This was reported in https://github.com/quarto-dev/quarto-actions/issues/98

Simple document:

---
title: test
jupyter: julia-1.10
---

```{julia}
1 + 1
```

Only Julia is available no python, and it is configured using https://quarto.org/docs/computations/julia.html#installation

using Pkg
Pkg.add("IJulia")
using IJulia
notebook()

Using quarto render test.qmd will throw an error

quarto render test.qmd
Check file:///quarto-cli/src/quarto.ts
ERROR: Jupyter kernel 'julia-1.10' not found.

Stack trace:
    at jupyterKernelspecFromMarkdown (file:///quarto-cli/src/core/jupyter/jupyter.ts:514:9)
    at async quartoMdToJupyter (file:///quarto-cli/src/core/jupyter/jupyter.ts:281:34)
    at async createNotebookforTarget (file:///quarto-cli/src/execute/jupyter/jupyter.ts:551:14)
    at async Object.target (file:///quarto-cli/src/execute/jupyter/jupyter.ts:183:12)
    at async fileExecutionEngineAndTarget (file:///quarto-cli/src/execute/engine.ts:213:18)
    at async renderFileInternal (file:///quarto-cli/src/command/render/render-files.ts:429:32)
    at async renderFiles (file:///quarto-cli/src/command/render/render-files.ts:310:9)
    at async render (file:///quarto-cli/src/command/render/render-shared.ts:87:18)
    at async Command.fn (file:///quarto-cli/src/command/render/cmd.ts:212:26)
    at async Command.execute (file:///quarto-cli/src/vendor/deno.land/x/cliffy@v0.25.4/command/command.ts:1790:7)

it is working in 1.3.450 but fails this way with new 1.4 version

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.