[Defect] WSL paths don't work

[tomk-amd]

From user feedback:

"If I try to load a dataset from a WSL directory and not in the C:\ drive, it fails to load and I get no error message. it took me a while to realize I had to copy the file from \wsl.localhost\Ubuntu to the C:\ drive"

To reproduce start a WSL session, copy a trace to the WSL filesystem.

Try to open it using file dialog or command line ex:

roc-optiq.exe -f \\wsl.localhost\Ubuntu\home\tkarczew\projects\rocpd-transpose.db

The following appears in the log.

[2026-05-01 16:53:17.875] [roc-optiq-log] [info] Opening file: \\wsl.localhost\Ubuntu\home\tkarczew\projects\rocpd-transpose.db
[2026-05-01 16:53:27.591] [roc-optiq-log] [debug] Detect table error 
[2026-05-01 16:53:27.592] [roc-optiq-log] [debug] 5
[2026-05-01 16:53:27.592] [roc-optiq-log] [debug] :
[2026-05-01 16:53:27.593] [roc-optiq-log] [debug] database is locked
[2026-05-01 16:53:27.621] [roc-optiq-log] [debug] Detect table error 
[2026-05-01 16:53:27.622] [roc-optiq-log] [debug] 5

[tomk-amd]

SQLite is unusually sensitive to that boundary because it depends on filesystem locking semantics.

For this path:

\\wsl.localhost\Ubuntu\home\tkarczew\projects\rocpd-transpose.db

a Windows process is opening a SQLite database that physically lives inside the WSL/Linux ext4 filesystem. Access goes through WSL’s Windows file-sharing bridge. That bridge is fine for ordinary file reads/writes, but SQLite relies on precise lock behavior: byte-range locks, shared/reserved/exclusive locks, and, in WAL mode, sidecar files like:

rocpd-transpose.db-wal
rocpd-transpose.db-shm

Those locks and shared-memory-style WAL coordination do not behave like a clean local filesystem when crossed between Linux and Windows. So SQLite may conclude the database is locked even when it looks like “just a file path” from Windows.