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

lookout-sdk doesn't support short sha1 in from/to arguments #369

Open
smacker opened this issue Nov 28, 2018 · 5 comments
Open

lookout-sdk doesn't support short sha1 in from/to arguments #369

smacker opened this issue Nov 28, 2018 · 5 comments
Labels
blocked Can not be started or continued for external limitations enhancement New feature or request

Comments

@smacker
Copy link
Contributor

smacker commented Nov 28, 2018

sdk review ipv4://127.0.0.1:2022 --from 9c3b4a2
[2018-11-28T12:59:58.820488+01:00]  INFO resolving to/from references app=lookout-sdk
base revision '9c3b4a2' error: reference not found

but

sdk review ipv4://127.0.0.1:2022 --from 9c3b4a28bd59526cc50164b467e75ceced403fc3

work fine

@carlosms carlosms added the enhancement New feature or request label Nov 28, 2018
@smacker
Copy link
Contributor Author

smacker commented Nov 29, 2018

Currently go-git doesn't support short hashes.

@dpordomingo dpordomingo added the blocked Can not be started or continued for external limitations label Jan 11, 2019
@carlosms
Copy link
Contributor

carlosms commented Apr 4, 2019

why don't we just change the error message? to something like:
short sha1 reference is not supported, please use the full 40 characters

@smacker
Copy link
Contributor Author

smacker commented Apr 4, 2019

because it's convenient to support short sha1s.

git log --oneline
/find commit from which we want to test
<copy-past to --from and run>
base revision '9c3b4a2' error: reference not found

@carlosms
Copy link
Contributor

carlosms commented Apr 4, 2019

I think we all agree it's convenient and it would be nice to support it if possible.

But given that this depends on support from go-git, and it's been stuck for months, I propose to change the error message to clarify that you need to use the full sha1.
Then my question is if that's good enough to close this issue, or if that's a temporary workaround and we should keep this issue open.

@smacker
Copy link
Contributor Author

smacker commented Apr 4, 2019

It makes sense to improve error message disregard of this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked Can not be started or continued for external limitations enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants