Octokit.NET VS AWS SDK

I'm testing out GitHub's Octokit for the first time (so ignore the magic strings in my code). I immediately hit a weird problem, where awaiting an Octokit function would just hang indefinitely - no return, no exception.

To interact with the GitHub API, let's install the Octokit.NET library with dotnet add package Octokit, then instantiate a client as simply as:

Does Octokit do what you want? https://github.com/octokit/octokit.net

Please look into the attached document for more details, https://github.com/aws/aws-sdk-net/files/12968773/AWS_V2_accesstoken_error.docx

I've taken the source code from the GitHub page of the project. If you need the exact version, here's the commit SHA: 93a94821dc8ff7a0073b74def6549728da3b51c7.

I was able to find the github in 5 minutes. https://github.com/aws/aws-sdk-net

See: * (CLI) https://docs.aws.amazon.com/cli/latest/reference/sts/assume-role.html * (.NET SDK) https://github.com/aws/aws-sdk-net/blob/master/sdk/test/Services/SecurityToken/IntegrationTests/AssumeRole.cs

Looking at the code for the AWS SDK for .NET, I suspect the culprit of the slow initialization is the endpoints.js file. This 700+ KB megalodon JSON file is parsed every time the AWS SDK is initialized. Since this happens in the AWS Core assembly, this penalty is incurred by all AWS service clients.

I have created an issue on Github but maybe someone has met such an issue before and knows a workaround?

i googled it for you. https://github.com/aws/aws-sdk-net/issues/1649.

While SigV4 is embedded in all the AWS SDKs, it is not exposed to being used independently (e.g., API Gateway requires SigV4 signatures on requests that can't be made through the SDK).

Does this help? https://github.com/aws/aws-sdk-net/tree/master/extensions/src/AWSSDK.Extensions.NETCore.Setup

I'm not trying to criticize their implementation though, I think it is sound but perhaps a bit overwrought in this particular area. I will, on the other hand, level some criticism against the AWS implementation, yikes.