Bobby Reed

Results 18 comments of Bobby Reed

I am trying to retrieve all Issue events for a repository. I worked around another bug with Int32 MaxValues, but I get back 40000 results now. I'm suspicious of round...

Sure. https://github.com/MicrosoftDocs/azure-docs

I'm still having the issue, so I'm not sure what to do.

Good Morning All, Sorry for being absent, but good to see the conversation continued. I'm getting this same error again today on another benign call. ``` currentBranches = await _client.Git.Reference.GetAll(From.owner,...

Even more oddly, it works in all cases when invoked from PowerShell, but not from C#. I tested with .50 in C# and it failed, so I have a PS...

Still Getting this error. ┌[ GLaDOS ] [  main ≣ ~3 -0 ! ] └[~\source\docindex]> $prs = $gitHubClient.PullRequest.GetAllForRepository("MicrosoftDocs", "azure-docs-pr", $request) ┌[ GLaDOS ] [  main ≣ ~3 -0...

C# Stack Trace (.50) at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode() at Octokit.GraphQL.Connection.d__25.MoveNext() at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult() at Octokit.GraphQL.Core.SimpleQuery`1.Runner.d__10.MoveNext() at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at Octokit.GraphQL.ConnectionExtensions.d__2`1.MoveNext() at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at...

OmniSharp has not updated their library today, and in normal VS Code the issue is resolved after the first delay and in insiders the issue is still there after the...

I should mention as well that the only recent change to my code base did not cause this issue as it was working fine for me and a colleague until...

I should mention as well that the only recent change to my code base did not cause this issue as it was working fine for me and a colleague until...