GithubClient | Github API client implemented on top of Dagger 2 DI | Dependency Injection library

Normally, an API client would be registered as a singleton as it must be thread-safe. In that case, the wrapped instance of RestClient, as well as its internal HttpMessageHandler (HttpClient is not that important here), will be a singleton.

Basically, a plethora of issues of RestSharp was related to its use of the legacy HttpWebRequest, which had a primitive HttpClient caching inside. RestRequest, and, consequently, HttpWebRequest, used to have a number of properties that triggered instantiation of a new HttpMessageHandler when those properties were changed. And that caused all the issues you can possibly imagine, which are retailed in Microsoft docs.

Your question reminded me that HttpClient is disposable, but the current RestClient is not (as per v107.0.4), so I will add it in the next patch.

You can mock repositoryService and gitHubClient to test various scenarios.

You can provide a package-level setter for these fields. It is a great idea to annotate it with Guava VisibleForTesting annotation.

Then you need to set mocks before the actual test on the instance.

Pseudocode for mocking

I'm not sure if there's an #exists? method or similar, which would probably be a better solution (I can't see such a method in the documentation!...), but you could always just rescue the exception in order to handle an expected failure gracefully. For example:

For anyone interested in doing this in the future, I figured out the solution.

1. I needed to revise the request object structure
2. Rather than using an authentication interceptor, I instead added an access token to the header. Here is where you can create access tokens for Github, you only need to grant it permissions to the 'repos' options for this use case to work.

This is what my updated request object looks like:

SOLVED:

I could not solve this entirely using the GitHubClient, so I am still interested to know if that is possible.

However, I managed to solve this by adding a WebClient to take care of the download after finding the ZipballUrl using Octokit. This had to be configured with User-Agent and Authorization headers to work.

Yes, a type annotation will allow you to select the method override that you want:

With certain assumptions like you are storing json data in your cache below is how I will try. Errors not handled.

Finally i get what was wrong, i was creating a credential, but that credential hadn't been asigned to the client.

So for the application that client was anonymous and ofc couldn't create a file.

now i am going to try to put as message the json itself, but i suppose this question is finish.

This is purely a GraalVM issue and to workaround it the only way (I know of other than changing the code in the actual libraty) is to create an Quarkus extension which would substitute the offending pieces of the library.