DateTime parsing issue in RAG

[eerojaaskelainen]

Greetings!

There seems to be an issue with dateTime parsing. Logs report:

[15.00.16.019] [INFO] [AGENT] Updating 624 files in persistent storage...
[15.02.30.810] [INFO] [AGENT] Starting differential SQLite sync...
[15.02.31.948] [ERROR] [GENERAL] [RAG] Failed to read DB snapshot
[Exception] FormatException: String was not recognized as a valid DateTime.
[StackTrace]    at System.DateTimeParse.Parse(String s, DateTimeFormatInfo dtfi, DateTimeStyles styles)
   at Microsoft.Data.Sqlite.SqliteValueReader.GetDateTime(Int32 ordinal)
   at LocalPilot.Services.ProjectContextService.<GetFileHashesFromDbAsync>d__13.MoveNext()

[15.02.32.034] [INFO] [AGENT] Updating 624 files in persistent storage...
[15.02.41.377] [INFO] [AGENT] Starting differential SQLite sync...
[15.02.42.510] [ERROR] [GENERAL] [RAG] Failed to read DB snapshot
[Exception] FormatException: String was not recognized as a valid DateTime.
[StackTrace]    at System.DateTimeParse.Parse(String s, DateTimeFormatInfo dtfi, DateTimeStyles styles)
   at Microsoft.Data.Sqlite.SqliteValueReader.GetDateTime(Int32 ordinal)
   at LocalPilot.Services.ProjectContextService.<GetFileHashesFromDbAsync>d__13.MoveNext()

[15.02.42.601] [INFO] [AGENT] Updating 624 files in persistent storage...
[15.03.36.953] [INFO] [AGENT] Starting differential SQLite sync...
[15.03.38.083] [ERROR] [GENERAL] [RAG] Failed to read DB snapshot
[Exception] FormatException: String was not recognized as a valid DateTime.
[StackTrace]    at System.DateTimeParse.Parse(String s, DateTimeFormatInfo dtfi, DateTimeStyles styles)
   at Microsoft.Data.Sqlite.SqliteValueReader.GetDateTime(Int32 ordinal)
   at LocalPilot.Services.ProjectContextService.<GetFileHashesFromDbAsync>d__13.MoveNext()

System is running on Finnish locale (fi_FI), wondering that could that affect?

[JalpeshVadgama]

@eerojaaskelainen Thank you for posting this issue

When the indexing service writes file modification timestamps (fileInfo.LastWriteTime) to the SQLite database, it was doing so using .ToString("yyyy-MM-dd HH:mm:ss") without specifying a culture. On machines with regional/culture settings where the time separator is not a colon (e.g. some European locales use .), the time separator was replaced locally. When the indexer subsequently tried to read the snapshot using reader.GetDateTime(1), SQLite's internal parser failed to recognize this custom culture-dependent string, throwing a fatal FormatException which crashed database synchronization loop.

I have made changes in following commit
d7faffa

This handles both legacy and newly formatted dates safely without needing to clear the database cache.

[JalpeshVadgama]

@eerojaaskelainen this is live with version 1.9.5. Do let me know if still an issue

[JalpeshVadgama]

did you face any issue? after upgrading to 1.9.5 @eerojaaskelainen

[eerojaaskelainen]

Hi! Pardon the delay in my reply... But seems to be fixed now.

[JalpeshVadgama]

@eerojaaskelainen thank for confirming. What kind of other features you like to see in upcoming release.