I am encountering a peculiar bug where Quarto fails to execute when run through the QGIS R Provider via an RSX script. Here's a detailed rundown of the behaviour:
When I execute the command Sys.which("quarto") via QGIS R Provider, it results in an empty string (""). Moreover, when I try to retrieve the system environment variable with Sys.getenv("PATH") via QGIS R Provider, it does not return Quarto.
Interestingly, this issue does not persist across all environments. In RStudio, both commands execute correctly. For instance, running Sys.which("quarto") returns "/usr/local/bin/quarto". Therefore, it seems the problem is specific to QGIS's R Provider.
It seems to mirror the behaviour observed with the R Provider. This indicates that the issue might not be specific to the R Provider in QGIS but more broadly related to how QGIS is managing or accessing the system's environment variables. Any ideas on why this could be the case?
dindiarto
commented
11 months ago
I am encountering a peculiar bug where Quarto fails to execute when run through the QGIS R Provider via an RSX script. Here's a detailed rundown of the behaviour:
When I execute the command
Sys.which("quarto")via QGIS R Provider, it results in an empty string (""). Moreover, when I try to retrieve the system environment variable withSys.getenv("PATH")via QGIS R Provider, it does not return Quarto.Interestingly, this issue does not persist across all environments. In RStudio, both commands execute correctly. For instance, running
Sys.which("quarto")returns"/usr/local/bin/quarto". Therefore, it seems the problem is specific to QGIS's R Provider.