chylex / Discord-History-Tracker

Desktop app & browser script that saves Discord chat history into a file, and an offline viewer that displays the file.
https://dht.chylex.com
MIT License
475 stars 83 forks source link

Getting "Error" when Click "Start Tracking" despite Server status Ready #245

Closed TiffanyNeat closed 11 months ago

TiffanyNeat commented 11 months ago

Once again, I am running on Linux (SteamOS). I have upgraded my archive.dht, waited until the internal server says "Ready", and entered the Tracking Script. I get the repeated error "DevTools failed to load source map: Could not load content for <file path to my discord install, which is a flatpak>/config/discord/0.0.39/modules/discord_desktop_core/core.asar/app/node_modules/@sentry-internal/tracing/cjs/browser/web-vitals/getFID.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE" in the console, and clicking on Start Tracking simple causes results in the Error output w/ no pop-up. This is off the newest update.

chylex commented 11 months ago

"DevTools failed to load source map" is not related to anything DHT does. What do you see in the Network tab if you look only at requests to the internal server?

image

TiffanyNeat commented 11 months ago

"DevTools failed to load source map" is not related to anything DHT does. What do you see in the Network tab if you look only at requests to the internal server?

image

Screenshot_20231221_062711 I see this. Also says "POST http://127.0.0.1:50000/track-messages 500 (Internal Server Error)" in the Console when I try again, now. Screenshot_20231221_063121

TheTechRobo commented 11 months ago

Try running DHT from a command line and seeing what it outputs?

TiffanyNeat commented 11 months ago

Try running DHT from a command line and seeing what it outputs?

Smart! Once I did this, a click of "Start Tracking" outputs in my terminal the following:

[ERROR] [BaseEndpoint] Microsoft.Data.Sqlite.SqliteException (0x80004005): SQLite Error 1: 'table attachments has no column named normalized_url'.
[ERROR] [BaseEndpoint]    at Microsoft.Data.Sqlite.SqliteException.ThrowExceptionForRC(Int32, sqlite3)
[ERROR] [BaseEndpoint]    at Microsoft.Data.Sqlite.SqliteCommand.PrepareAndEnumerateStatements()+MoveNext()
[ERROR] [BaseEndpoint]    at Microsoft.Data.Sqlite.SqliteCommand.GetStatements()+MoveNext()
[ERROR] [BaseEndpoint]    at Microsoft.Data.Sqlite.SqliteDataReader.NextResult()
[ERROR] [BaseEndpoint]    at Microsoft.Data.Sqlite.SqliteCommand.ExecuteReader(CommandBehavior)
[ERROR] [BaseEndpoint]    at Microsoft.Data.Sqlite.SqliteCommand.ExecuteReader()
[ERROR] [BaseEndpoint]    at Microsoft.Data.Sqlite.SqliteCommand.ExecuteNonQuery()
[ERROR] [BaseEndpoint]    at DHT.Server.Database.Sqlite.SqliteDatabaseFile.AddMessages(Message[] messages)
[ERROR] [BaseEndpoint]    at DHT.Server.Endpoints.TrackMessagesEndpoint.Respond(HttpContext ctx)
[ERROR] [BaseEndpoint]    at DHT.Server.Endpoints.BaseEndpoint.Handle(HttpContext ctx, StringValues token)
chylex commented 11 months ago

Strange, looks like the database didn't get upgraded properly. Can you try opening it in DB Browser for SQLite (or some other db viewer if you already have one), and show the layout of attachments and downloads tables?

image

EDIT: In case someone finds this screenshot later on, this is an example of a database after an interrupted upgrade, not how it's supposed to look. I randomly opened one of my test files and it happened to be a broken one lol.

TiffanyNeat commented 11 months ago

Strange, looks like the database didn't get upgraded properly. Can you try opening it in DB Browser for SQLite (or some other db viewer if you already have one), and show the layout of attachments and downloads tables?

image

Oh, damn. That's... definitely because it just didn't. My app hard crashed while it was doing the process, and I was up-until-now under the impression that it finished successfully & just did that for some reason. Thank gods I had a backup of the pre-upgraded version as suggested LOL, I'm re-upgrading with the newest update version, so unless this one goes wrong as well I'll close this Issue once it's done.

TiffanyNeat commented 11 months ago

Closing this issue as it is solved, all I had to do was re-upgrade the archive database I was using, which was done successfully on retry. Remember to backup your databases in case this happens to you, as I had to use a backup of mine to re-upgrade it.

TheTechRobo commented 11 months ago

Perhaps the app should put a flag into the database while it is updating it, so that it can detect an inconsistent database.