quarto-dev / quarto-dev/quarto-cli

[julia] `--no-execute-daemon` does not seem to work on Windows

Open
#10,353 0 comments 0 reactions 1 assignee View on GitHub

@cderv is already working on this.

Since Jul 22, 2024.

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

Description

Example does not matter much

---
title: "test"
engine: julia
---

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

I was trying to control the daemon behavior to change default, and start fresh at each render (for a debug session).
We mention support in the doc https://quarto.org/docs/computations/julia.html#worker-process-reuse

I get this the first time running

❯ quarto render index.qmd --no-execute-daemon
Starting julia control server process. This might take a while...
Julia server process started.
Running [1/1] at line 6:  2+1
pandoc
  to: html
  output-file: index.html
  standalone: true
  section-divs: true
  html-math-method: mathjax
  wrap: none
  default-image-extension: png

metadata
  document-css: false
  link-citations: true
  date-format: long
  lang: en
  title: test

Output created: index.html

And the second time, I would expect the server to have been closed and so Julia server restarted again but julia cell ran in same process

❯ quarto render index.qmd --no-execute-daemon
Running [1/1] at line 6:  2+1
pandoc
  to: html
  output-file: index.html
  standalone: true
  section-divs: true
  html-math-method: mathjax
  wrap: none
  default-image-extension: png

metadata
  document-css: false
  link-citations: true
  date-format: long
  lang: en
  title: test

Output created: index.html

https://github.com/quarto-dev/quarto-cli/blob/0d87b08a5c1b25ec6c6573e0bed793cd67eb6687/src/execute/julia.ts#L134
https://github.com/quarto-dev/quarto-cli/blob/0d87b08a5c1b25ec6c6573e0bed793cd67eb6687/src/execute/julia.ts#L518-L528

Maybe I am misunderstanding something, but it does not seem to be working as expected.

Same with --execute-daemon-restart and yaml version

execute:
  daemon: false

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.