Open javajon opened 1 year ago
Thanks for the report. I don't think there's a way for us to verify the integrity of the installation like you suggested; our checking of the version is effectively checking for its integrity the best way we can outside of attempting to render something (which is causing the error).
Do you have a theory for how/why your installation was corrupt?
Bug description
Using the latest Quarto with version with latest tools on Windows 11, VSCode:
In _quarto.yml:
With this qmd:
In exploring the notion that
mf.dll
might be missing the research found thatmf.dll
is related to Media Foundation features in Windows 11. I verified that the media player feature is enabled and installed in this Windows machine and ran "DISM.exe /Online /Cleanup-image /Scanhealth" to verify the integrity of the Windows 11 installation. The C:\Windows\System32\mf.dll file is present and appears to be the expected size. All appears healthy and normal. Both the Windows Player and legacy player are present and functional.Then in reading the docs more, quarto says that the chromium engine/plugin is used to render the output. The tools list says its the latest, but I suspected the installation was corrupt and the tool list just verifies the version but not the integrity of its installation.
I uninstalled the chromium tool using
quarto tools uninstall chromium
then reinstalled withquarto tools install chromium
.The pdf rendering with mermaid worked after that.
Suggestions:
(Also, in the docs I think all the commands that read
quarto install [x]
should instead readquarto tools install [x]
.)