search

the-hideout / TarkovMonitor

Monitor Tarkov log files to help track progress, queues, and groups
GNU General Public License v3.0
91 stars 16 forks source link

clicking "read past logs" results in a state indistinguishable from being broken #69

Closed wchristian closed 4 months ago

wchristian commented 5 months ago

it opens this modal with a spinner, and then provides no further information or output, while simultaneously not seemingly using any cpu or io. clicking "OK" does not result in any change in the program whatsoever and clicking cancel just closes the modal

image image

cpjet64 commented 5 months ago

Having the exact same issue. Have tried relaunching as admin as well as game closed/open. When I click Raw Logs I get the following text: 2024-04-15 15:28:25.040 -04:00|Info|push-notifications|LongPollingWebSocketRequest result Count:74 MessageType:Text 2024-04-15 15:28:25.040 -04:00|Info|push-notifications|LongPollingWebSocketRequest received:74 2024-04-15 15:28:25.040 -04:00|Info|push-notifications|NotificationManager.ProcessMessage | Received Service Notifications ChannelDeleted 2024-04-15 15:28:25.040 -04:00|Info|push-notifications|LongPollingWebSocketRequest result Count:0 MessageType:Close 2024-04-15 15:28:25.040 -04:00|Info|push-notifications|LongPollingWebSocketRequest webSocket disposed

cpjet64 commented 5 months ago

Just confirmed this issue is only on the latest version of TM. Using TM v1.3.3.0 the Read Past Log Files Modal works fine and as expected but the processing results in a unhandled exception. image

see pastebin for output https://pastebin.com/eAAgh5bX

Razzmatazzz commented 4 months ago

The latest version has some tweaked error handling that should give a better idea of the point at which this error is occurring.