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

(GH-560) Consider short and long SHAs #561

Closed
wants to merge 1 commit into from

Conversation

chelnak
Copy link

@chelnak chelnak commented Aug 1, 2022

As pointed out in #560, the check for SHA equality only
currently works for long shas which are 40 characters.

If a short SHA with :revision rev-parse HEAD returns a long SHA
therefore rendering the equality check false.

e.g

"cb1eb6" != "cb1eb6bb33eb6889818f5b02aa593b4ff2f8ca33"

This commit updates the args so that rev-parse will always return a SHA
that is the same length as the value provided with the :revision
parameter.

This will cause the check to be true and exit get_revision early as it would
do when both values are 40 characters.

As pointed out in #560, the check for SHA equality only
currently works for long shas which are 40 characters.

If a short SHA with :revision rev-parse HEAD returns a long SHA
therefore rendering the equality check false.

e.g

"cb1eb6" != "cb1eb6bb33eb6889818f5b02aa593b4ff2f8ca33"

This commit updates the args so that rev-parse will always return a SHA
that is the same length as the value provided with the :revision
parameter.

This will cause the check to be true and exit get_revision early as it would
do when both values are 40 characters.
@github-actions
Copy link

github-actions bot commented Oct 1, 2022

Hello! 👋

This pull request has been open for a while and has had no recent activity. We've labelled it with attention-needed so that we can get a clear view of which PRs need our attention.

If you are waiting on a response from us we will try and address your comments on a future Community Day.

Alternatively, if it is no longer relevant to you please close the PR with a comment.

Please note that if a pull request receives no update for 7 after it has been labelled, it will be closed. We are always happy to re-open pull request if they have been closed in error.

@giggsey
Copy link

giggsey commented Oct 31, 2022

Could this be reopened, and the checks rerun. The logs have expired, and I'm curious to see what the failures were

@LukasAud
Copy link

LukasAud commented Nov 7, 2022

@giggsey looks like there was a set of 10 failures occurring across all tested OSs

@giggsey
Copy link

giggsey commented Nov 7, 2022

Thanks @LukasAud

My quick scanning looks like the change not handling when revision isn't used. I guess wrapping the new change in an if statement, and keeping the old logic in other scenarios would handle that

@LukasAud
Copy link

LukasAud commented Nov 7, 2022

@giggsey Thanks for looking into it. I'll let @chelnak of the possible fixes for these issues. I believe this PR is still a WIP and its been sitting stale for a bit. It probably needs re-evaluation and some more work on new test cases on top of those fixes.

@LukasAud
Copy link

LukasAud commented Nov 9, 2022

We have investigated and confirmed this issue. However, we cannot currently allocate any resources to completing this PR. This work is currently in our backlog but we cannot give an estimate of when we will be able to get onto it.

For now, we will be closing this PR to avoid keeping it stale and deterring other users from attempting to contribute a solution.

@LukasAud LukasAud closed this Nov 9, 2022
@Ramesh7 Ramesh7 deleted the GH-560-consider_short_shas branch June 6, 2024 15:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants