queryverse / VegaLite.jl

Julia bindings to Vega-Lite

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Plotting error in Pluto.jl. (Windows 10, Julia 1.6.0)

eliascarv opened this issue · comments

I can't show VegaLite plots in the PLuto.jl.
I'm using Julia 1.6.0 and Windows 10.
A screenshot of the error message can be seen below.
Could someone help me with this error please. Thanks in advance.
2021-03-26 (4)

Can you plot from the REPL? Generally, there seems to be a permission problem: VegaLite.jl needs to spawn the node version that NodeJS.jl installs, and for some reason that seems not to work on your system.

Yes, I can plot from REPL:

20210326_190325

I uninstalled Julia and installed it again, then ran Julia and Pluto.jl from the terminal. Unfortunately, I continued to receive an error message:

2021-03-26 (6)

I think maybe I should run Julia as an administrator.

Ah, actually, I asked you to do the wrong thing :) Displaying plots from the REPL doesn't start the node stuff because the Javascript ends up just running in the browser. BUT, saving a plot should. Could you try to save your plot from the REPL both as an svg and a png or pdf file, and see whether that works?

You could also check whether that node.exe file exists that is shown in the error message exists on your system.

As you asked I tried to save the plot. And I got an error message.
Error message:

Captura de tela 2021-03-27 104237
Captura de tela 2021-03-27 104712
Captura de tela 2021-03-27 104753

I also checked that node.exe is in the files in the .julia folder, and it is there:

Captura de tela 2021-03-27 104920

In the error message it is saying that the ImageIO package is not installed.
That's it? Do I need this package to use VegaLite?

I think the problem is actually just that Julia 1.6 broke NodeJS.jl with a change to how it handles artifacts on Windows, and so my best guess is that that is explaining the error. I'm trying to fix that now, might be worth checking again in a few days, once I've published new versions of those packages.

OK, thank you for the attention.

Could you try again? I pushed a new NodeJS version that I believe should fix this.

Now works! Thanks