Add-on does not always remove public dependency folder after failed dependency installation #42
Labels
bug
Something isn't working
good first issue
Good for newcomers
help wanted
Extra attention is needed
The cause of this issue #14 was antivirus blocking part of dependency installation. While the error did show up in the output, it seems the dependencies folder was not removed after the failed installation, causing the add-on to get into a bad state where dependencies are partially installed. Since public_dependencies exists, it would never prompt to install dependencies again.
This is likely a similar issue to #20, also the cause of this devforum bug report
The text was updated successfully, but these errors were encountered: