Closed Corrupt-Specturion closed 2 years ago
No idea what kind of message is causing this, but I can improve the error handling and 1) track messages near the error, and 2) show more information in the log.
Please try this beta release and watch the browser console for errors. It should not stop tracking anymore when it encounters an error, but it will still print the error with more details that could help me understand why the error happens.
Can you please expand this part using the arrows?
{className: "message-XB61Zl", children: Array(5), onClick: ƒ}
Should be enough to expand down to two levels, i.e. click the arrow and then click any additional arrow that appears. Mind there might be personal information in the expanded parts, so please censor anything that includes names or long strings of numbers.
Looks like it's a server boost message, but if I look at server boost messages on my server DHT doesn't show any warnings. Could you please expand children -> 3
like this?
3: cannot be expanded
Can you send a screenshot of just children
expanded?
Interesting, I looked at server boost messages from 2019 to now, and none of them look like this. Regardless, DHT doesn't track boost messages so as long as they don't break tracking anymore, I'll consider it resolved.
In both release version 35.3 and 36.1, the tracker will stop at certain points in only one channel. There doesn't seem to be anything out of the ordinary when it stops. When I scroll up, it resumes tracking, but does not track the portion it stopped at.
discordapp.com-1654497068995.log
This is a log captured from the error message in the Discord client's console from one of the stopping points. All of the stopping points' console errors look to be about the same content-wise. No errors appear in the actual terminal used to run DHT, however.
I am running on Linux Mint Mate 20.2, kernel version 5.4.0-113-generic, using the latest Discord tar.gz client.