C＃Web API调用错误消息

Question

I am using the C# wrapper HaloEzAPI

When I make a call using GetCustomPostGameCarnageReport I get the following error message.

It wasnt happening two days ago and just suddenly started.

It says the error occurs on line 56 below. If anyone could help me with this it would be appreciated greatly.

Number must be either non-negative and less than or equal to Int32.MaxValue or -1.
Parameter name: millisecondsTimeoutDescription: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.ArgumentOutOfRangeException: Number must be either non-negative and less than or equal to Int32.MaxValue or -1.
Parameter name: millisecondsTimeout
Source Error:
Line 54: if (results.Id.MatchId != null)
Line 55: {
Line 56: var carnageReports = await _service.GetCustomPostGameCarnageReport(results.Id.MatchId);

I also get this error occasionally

JSON integer 4294967295 is too large or small for an Int32. Path 'TeamStats[0].Score', line 1, position 2413.Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: Newtonsoft.Json.JsonReaderException: JSON integer 4294967295 is too large or small for an Int32. Path 'TeamStats[0].Score', line 1, position 2413.
Source Error:
Line 54: if (results.Id.MatchId != null)
Line 55: {
Line 56: var carnageReports = await _service.GetCustomPostGameCarnageReport(results.Id.MatchId);

Answer 1

According to errors that you provide:

• second error description says very clear: value that json serialized tries to serialize as an integer is too big for it. Actually, in your TeamStats[0].Score at the time of error occured you have value 4294967295 , but max int value in .net is 2147483647 . So maybe it's better to use long instead of int (and even more instead of uint for not to be outside of its max value if you really have so big values);

• in my opinion, error from the first description is possibly related to the same problem with the int max value. If it's possible to post more detailed stack trace of you timeout problem so we can try to dive deeper with it and help you