Open cxumol opened 2 years ago
@andelf Sorry for incorrectly indicating it being an "upstream" bug. The upstream (nodejs) issue I mentioned was closed in 2016, which means to me that they have resolved it on their side and thus won't make any further change since 2016.
As of this bug, I do believe it can be fixed on the Logseq side, because there has been a solution made from another project when they encounter the same/similar problem. The same/similar issue on facebook/jest https://github.com/facebook/jest/issues/6880 And how they resolved it https://github.com/facebook/jest/pull/6906/files
@cxumol Many thanks for providing the details. A minor patch to fs utility should fix this.
+1
This is a problem in other electron apps also, such as Arduino IDE 2. I use a small batch script as a temporary workaround for starting Logseq with a custom TEMP dir on a normal drive, which is only needed when installing new plugins.
@ECHO OFF
Pushd %LOCALAPPDATA%\Logseq\app-0.9.4
set TEMP=C:\tmp&& %LOCALAPPDATA%\Logseq\Logseq.exe
What happened?
Unable to install anything (plgins/themes) from marketplace. It must be caused by my temp folder setup, which is located in the RAMDISK.
Error messages are like
Reproduce the Bug
Expected Behavior
No response
Screenshots
Desktop Platform Information
APP v0.6.3 on Windows 10
Mobile Platform Information
No response
Additional Context
It seems similar to this upstream bug https://github.com/nodejs/node/issues/6861
The possible solution might be this one https://github.com/facebook/jest/pull/6906 Thanks