find-any-file: fix checksum #197107
Merged
find-any-file: fix checksum #197107
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
echocrow
force-pushed
the
find-any-file-v2.5.5
branch
from
27fc20c to
c8fb685
Compare
8 tasks
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.
Checksum for
find-any-fileappears to be incorrect for v2.5.5; seems to be a regression from #197051.This PR fixes the expected checksum.
v2.5.4 checksum ✅:
ded32d0c8589562a721c3708f7a1425923d3f96dc19af7f2e5ef3e878aebea54ded32d0c8589562a721c3708f7a1425923d3f96dc19af7f2e5ef3e878aebea54v2.5.5 checksum ❌:
9f7d95fec1124517877c6621fb68f392830ad75010784cb7070bdb31bd446ec757ef75b7ee92e9d27a570d4e878e4e1ccd2805456411f089bf0459224c555f2bThat said, I suspect PR #197051 was created automatically. Unsure what caused the checksum mismatch, and whether there is a deeper-rooted bug to be fixed(?).