Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add-on does not always remove public dependency folder after failed dependency installation #42

Open
Nightriff opened this issue Jan 31, 2024 · 0 comments
Labels
bug Something isn't working good first issue Good for newcomers help wanted Extra attention is needed

Comments

@Nightriff
Copy link
Collaborator

Nightriff commented Jan 31, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant