search

Aireil / FFLogsViewer

Dalamud plugin to view FF Logs ranking percentiles in-game
47 stars 16 forks source link

Networking error, please try again #20

Closed Moo-Chicken closed 2 years ago

Moo-Chicken commented 2 years ago

When I look at the logs of my own character it loads half my logs stopping at UWU, which I think it has to do with my only UWU parse for this expansion not being locked in yet, error it gives below.

image

2022-04-24 21:49:55.791 -05:00 [ERR] [FFLogsViewer] Networking error
System.FormatException: Input string was not in a correct format.
   at System.Number.ThrowOverflowOrFormatException(ParsingStatus status, TypeCode type)
   at System.Number.ParseInt32(ReadOnlySpan`1 value, NumberStyles styles, NumberFormatInfo info)
   at System.String.System.IConvertible.ToInt32(IFormatProvider provider)
   at System.Convert.ChangeType(Object value, Type conversionType, IFormatProvider provider)
   at Newtonsoft.Json.Utilities.ConvertUtils.TryConvertInternal(Object initialValue, CultureInfo culture, Type targetType, Object& value)
   at Newtonsoft.Json.Utilities.ConvertUtils.Convert(Object initialValue, CultureInfo culture, Type targetType)
   at Newtonsoft.Json.Linq.JValue.JValueDynamicProxy.TryConvert(JValue instance, ConvertBinder binder, Object& result)
   at CallSite.Target(Closure , CallSite , Object )
   at FFLogsViewer.CharData.ParseZone(Object zone) in D:\a\FFLogsViewer\FFLogsViewer\FFLogsViewer\CharData.cs:line 305
   at FFLogsViewer.CharData.<FetchData>b__17_0() in D:\a\FFLogsViewer\FFLogsViewer\FFLogsViewer\CharData.cs:line 152
2022-04-24 21:49:55.791 -05:00 [INF] LASTEXCEPTION:eyJXaGVuIjoiMjAyMi0wNC0yNFQyMTo0OTo1NS43OTE4ODQ5LTA1OjAwIiwiSW5mbyI6IlN5c3RlbS5Gb3JtYXRFeGNlcHRpb246IElucHV0IHN0cmluZyB3YXMgbm90IGluIGEgY29ycmVjdCBmb3JtYXQuXHJcbiAgIGF0IFN5c3RlbS5OdW1iZXIuVGhyb3dPdmVyZmxvd09yRm9ybWF0RXhjZXB0aW9uKFBhcnNpbmdTdGF0dXMgc3RhdHVzLCBUeXBlQ29kZSB0eXBlKVxyXG4gICBhdCBTeXN0ZW0uTnVtYmVyLlBhcnNlSW50MzIoUmVhZE9ubHlTcGFuYDEgdmFsdWUsIE51bWJlclN0eWxlcyBzdHlsZXMsIE51bWJlckZvcm1hdEluZm8gaW5mbylcclxuICAgYXQgU3lzdGVtLlN0cmluZy5TeXN0ZW0uSUNvbnZlcnRpYmxlLlRvSW50MzIoSUZvcm1hdFByb3ZpZGVyIHByb3ZpZGVyKVxyXG4gICBhdCBTeXN0ZW0uQ29udmVydC5DaGFuZ2VUeXBlKE9iamVjdCB2YWx1ZSwgVHlwZSBjb252ZXJzaW9uVHlwZSwgSUZvcm1hdFByb3ZpZGVyIHByb3ZpZGVyKVxyXG4gICBhdCBOZXd0b25zb2Z0Lkpzb24uVXRpbGl0aWVzLkNvbnZlcnRVdGlscy5UcnlDb252ZXJ0SW50ZXJuYWwoT2JqZWN0IGluaXRpYWxWYWx1ZSwgQ3VsdHVyZUluZm8gY3VsdHVyZSwgVHlwZSB0YXJnZXRUeXBlLCBPYmplY3QmIHZhbHVlKVxyXG4gICBhdCBOZXd0b25zb2Z0Lkpzb24uVXRpbGl0aWVzLkNvbnZlcnRVdGlscy5Db252ZXJ0KE9iamVjdCBpbml0aWFsVmFsdWUsIEN1bHR1cmVJbmZvIGN1bHR1cmUsIFR5cGUgdGFyZ2V0VHlwZSlcclxuICAgYXQgTmV3dG9uc29mdC5Kc29uLkxpbnEuSlZhbHVlLkpWYWx1ZUR5bmFtaWNQcm94eS5UcnlDb252ZXJ0KEpWYWx1ZSBpbnN0YW5jZSwgQ29udmVydEJpbmRlciBiaW5kZXIsIE9iamVjdCYgcmVzdWx0KVxyXG4gICBhdCBDYWxsU2l0ZS5UYXJnZXQoQ2xvc3VyZSAsIENhbGxTaXRlICwgT2JqZWN0IClcclxuICAgYXQgRkZMb2dzVmlld2VyLkNoYXJEYXRhLlBhcnNlWm9uZShPYmplY3Qgem9uZSkgaW4gRDpcXGFcXEZGTG9nc1ZpZXdlclxcRkZMb2dzVmlld2VyXFxGRkxvZ3NWaWV3ZXJcXENoYXJEYXRhLmNzOmxpbmUgMzA1XHJcbiAgIGF0IEZGTG9nc1ZpZXdlci5DaGFyRGF0YS48RmV0Y2hEYXRhPmJfXzE3XzAoKSBpbiBEOlxcYVxcRkZMb2dzVmlld2VyXFxGRkxvZ3NWaWV3ZXJcXEZGTG9nc1ZpZXdlclxcQ2hhckRhdGEuY3M6bGluZSAxNTIiLCJDb250ZXh0IjoiW0ZGTG9nc1ZpZXdlcl0gTmV0d29ya2luZyBlcnJvciJ9
Aireil commented 2 years ago

It was indeed because the log was new, the API sends some weird data when that happens. Fixed in 2.0.3.1, thank you for the report!