-
-
Notifications
You must be signed in to change notification settings - Fork 814
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
Failed dependency installations are incorrectly reported as successful #1605
Comments
If a depenency is unavailable for current platform or version of Sublime Text, Package Control currently considders the dependency not to be required. Therefore it's handled as success. Not sure about the origin, if a package doesn't require a library on a certain platform or version of Sublime Text, it should be defined correctly in |
Dependency installations can fail for a variety of reasons, for example due to incompatible architectures as described in #1425.
Currently package control logs that the installation could not be performed, just after that it logs that the dependency was installed and shows a popup to the user suggesting an application restart to reload it.
There's a lot of similar or related bug reports already, however, I haven't found one detailing this specific issue, as most of them focus on the failure reason, not the incorrect reporting.
This bug is not about
lxml
not being available on my platform but about the incorrect notification that dependencies were successfully installed with no notification outside the Console about the installation failure.Example:
The text was updated successfully, but these errors were encountered: