Better errors - git fails with a confusing error message when a commit doesn't exist in a git repo, used in a stack.yaml config #1453
Comments
It'd make sense to me to add a message like |
@mgsloan, Where this thing is processed? Where should one start to look to add this message? |
mrkkrp
added a commit
to mrkkrp/stack
that referenced
this issue
Dec 10, 2015
It's fixed, thanks @mrkkrp
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello everybody, this is a casual issue and not immediately detrimental.
In a
stack.yaml
, if you set a source code location to a git commit that doesn't exist on the referenced repo, then you get the "could not parse object" error, which led me to believe I had somehow pasted my commit hash wrong. For instance, if you have this in yourstack.yaml
:and you tried to
stack build
, you would get the error:Which is misleading.
The text was updated successfully, but these errors were encountered: