Timeline API: Exception: {"Requested value 'reviewed' was not found."}

[aniket-aurea]

Note: gitHubClient.PullRequest.Get works fine for the same pull request
StackTrace:
at System.Enum.EnumResult.SetFailure(ParseFailureKind failure, String failureMessageID, Object failureMessageFormatArgument)
at System.Enum.TryParseEnum(Type enumType, String value, Boolean ignoreCase, EnumResult& parseResult)
at System.Enum.Parse(Type enumType, String value, Boolean ignoreCase)
at Octokit.Internal.SimpleJsonSerializer.GitHubSerializerStrategy.DeserializeObject(Object value, Type type) in C:\Users\shiftkey\code\octokit.net\Octokit\Http\SimpleJsonSerializer.cs:line 125
at Octokit.PocoJsonSerializerStrategy.DeserializeObject(Object value, Type type) in C:\Users\shiftkey\code\octokit.net\Octokit\SimpleJson.cs:line 1478
at Octokit.Internal.SimpleJsonSerializer.GitHubSerializerStrategy.DeserializeObject(Object value, Type type) in C:\Users\shiftkey\code\octokit.net\Octokit\Http\SimpleJsonSerializer.cs:line 166
at Octokit.PocoJsonSerializerStrategy.DeserializeObject(Object value, Type type) in C:\Users\shiftkey\code\octokit.net\Octokit\SimpleJson.cs:line 1505
at Octokit.Internal.SimpleJsonSerializer.GitHubSerializerStrategy.DeserializeObject(Object value, Type type) in C:\Users\shiftkey\code\octokit.net\Octokit\Http\SimpleJsonSerializer.cs:line 166
at Octokit.SimpleJson.DeserializeObject(String json, Type type, IJsonSerializerStrategy jsonSerializerStrategy) in C:\Users\shiftkey\code\octokit.net\Octokit\SimpleJson.cs:line 583
at Octokit.SimpleJson.DeserializeObject[T](String json, IJsonSerializerStrategy jsonSerializerStrategy) in C:\Users\shiftkey\code\octokit.net\Octokit\SimpleJson.cs:line 595
at Octokit.Internal.SimpleJsonSerializer.Deserialize[T](String json) in C:\Users\shiftkey\code\octokit.net\Octokit\Http\SimpleJsonSerializer.cs:line 21
at Octokit.Internal.JsonHttpPipeline.DeserializeResponse[T](IResponse response) in C:\Users\shiftkey\code\octokit.net\Octokit\Http\JsonHttpPipeline.cs:line 62
at Octokit.Connection.d__531.MoveNext() in C:\Users\shiftkey\code\octokit.net\Octokit\Http\Connection.cs:line 560 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Octokit.ApiConnection.<GetPage>d__401.MoveNext() in C:\Users\shiftkey\code\octokit.net\Octokit\Http\ApiConnection.cs:line 0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Octokit.ApiConnection.<>c__DisplayClass17_01.<<GetAll>b__0>d.MoveNext() in C:\Users\shiftkey\code\octokit.net\Octokit\Http\ApiConnection.cs:line 0 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Octokit.ApiPagination.<GetAllPages>d__01.MoveNext() in C:\Users\shiftkey\code\octokit.net\Octokit\Clients\ApiPagination.cs:line 0

[shiftkey]

@aniket-aurea do you have an example URL that I can use to confirm this is related to EventInfoState not having this value?

[ryangribble]

Apart from adding enum values that are missing and waiting for another release, we also have a proposal to handle these at runtime here #1504

[aniket-aurea]

Thanks, this sounds great. I don't have a url as this is a private repo. But I saw atleast 1 other status apart from the one mentioned in the ticket, that gave the same exception. Yes the problem did occur during de-serialization by Newtonsoft, as the Enum did not have the value. I have made this field string in my classes till a fix is available, and am using the rest API till then. Hope this helps. [image: Aurea] <http://go.aurea.com/e/23432/2015-11-05/3brlh6/1191512291> www.aurea.com

…

On Mon, Jan 9, 2017 at 10:15 AM, Ryan Gribble ***@***.***> wrote: Apart from adding enum values that are missing, we also have a proposal to handle these at runtime here #1504 <#1504> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1525 (comment)>, or mute the thread <https:/notifications/unsubscribe-auth/AVliLcx9Ybne0cy3jxmgn0dVkbU2ldd9ks5rQbuAgaJpZM4LW5fH> .