gin-cli does not write to stderr when a checkout fails #186
Comments
|
Interesting. gin-cli definitely detected the failure (error during clone command), so I don't know why it didn't throw out an error. In the current version, v0.15, this should have printed unknown error, which admittedly isn't helpful and has already bitten me in the behind once, but should have been an issue. If any error occurs, it exits with a non-zero status and N operations failed printed to stderr. Error conditions are handled a lot better than they used to be, but it looks like I need better fallback cases. |
|
Not sure if this is till the case. I think I covered any remaining error cases with the v0.16 release, but I'm bumping the priority and keeping it open to make sure I check everything. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This occurred during my testing of the GinUI client:
When a checkout fails for whatever reason (in this particular case presumably due to a timeout somewhere), gin-cli does not write anything to stderr. GinUI requires that, on failure, something is written to stderr (preferably something meaningful) to figure out whether or not gin-cli worked correctly.
Relevant portions of the gin-cli log:
The text was updated successfully, but these errors were encountered: