Fix ACCESS_KEYS#242
Open
nicegamer7 wants to merge 1 commit into
Open
Conversation
This file contains hidden or 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
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.
It looks like
ACCESS_KEYSbroke with 906e9a7 and d078ebe.The first commit caused the following issue:
After fixing the above issue, I found this issue caused by the second commit:
I used Claude Opus 4.6 to find solutions to these issues. This is how Claude described these issues:
hmac256opts(commit 906e9a7) —length: 512was added to the HMAC options, which breaksimportKeywhen the raw key data is shorter than 64 bytes. Fix: omitlengthfromhmac256optswhen no argument is passed, and havehkdfhmacpass512explicitly.hmacsign— missingasync/awaitoncrypto.subtle.sign, causingnormalize8to receive a Promise instead of an ArrayBuffer, silently returning an empty Uint8Array. Fix: makehmacsignasync andawaitthe sign call.