-
Notifications
You must be signed in to change notification settings - Fork 24
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
'AWS Signer SigV4A Headers' unit test failing #491
Comments
You could enable trace logging (https://github.com/awslabs/aws-crt-nodejs/blob/main/lib/native/io.ts#L87) and attach the log for that particular test. That being said, we do not have any access to Sonoma at present for testing purposes and I don't have an ETA when we would. |
Try modifying the test so that it swallows the error and doesn't fail. For me, I get:
|
Seems likely that something is failing in here that does not fail for any versions < 14: https://github.com/awslabs/aws-c-cal/blob/main/source/darwin/securityframework_ecc.c |
Thanks for reporting the issue. The latest version https://github.com/awslabs/aws-crt-nodejs/tree/v1.18.1, with the fix just released. It should be available from npm soon. The fix is here for visibility |
Okay, the latest version is available now, can you try it out and let us know if you still have any issue? |
Just updated and tested. Worked as expected. Amazing work and response time! |
I'm glad this fix worked for you, let us know if you run into any other problems with this repo. |
Describe the bug
I was testing the SigV4A signing examples from https://github.com/aws-samples/sigv4a-signing-examples and kept receiving the following credential error.
I then cloned this repo and ran the unit tests with "npm run test" and saw the same credentials error was occurring with the unit test.
I am running the latest macOS: 14.0 (23A344). I tried to debug it with vs code but the issue is in the c code. Any obvious areas to look or purge like keychain, some local aws cache, etc? I just have the standard default profile configured in ~/.aws/credentials and config.
Expected Behavior
I expect to see the signed headers returned.
Current Behavior
Failing on 'AWS Signer SigV4A Headers' unit test
Reproduction Steps
Possible Solution
No response
Additional Information/Context
No response
aws-crt-nodejs version used
1.18
nodejs version used
20.*
Operating System and version
macOS 14.0 (23A344)
The text was updated successfully, but these errors were encountered: