Fix for spitting error out when pip fails #813
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
When do y'all think this will get merged/released? |
|
@babyhuey - I'll try to release a new version in the coming days, thanks 🙇 |
Any update on getting a release out? It's really annoying for us to have to build locally when our pipelines fail with the wrong error |
|
Hey @babyhuey 👋 Thanks for the ping and sorry for the delay here, the new v6.1.0 should be out now |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This should help with this issue: #663
Currently, if pip fails, you just get a "Exited with code 1" that is entirely unhelpful and leads to people thinking they have other issues than dependency.
With this fix, it will spit out the error (if there is one)