DBPTK Desktop - Windows filepath causes unicode escape sequence error on SIARD load

[seso-kdrs]

When opening a SIARD file at a path containing "\u", an exception happens:

Log:

2025-12-11 15:43:16,164 [http-nio-auto-1-exec-4] WARN c.d.c.a.e.RestResponseEntityExceptionHandler - ERROR_ID: c6bbb461-47b8-4c32-b5f4-90b956a9e673 - RESTException: Could not query index, message: Error from server at http://localhost:18984/solr/dbv-databases_shard1_replica_n1/select?q=%28siard_path%3A%22C%3A%5Cupload%5Cdemo.siard%22%29&fq=%28content_type%3A%22database%22%29&sort=uuid+asc&start=0&rows=10&fl=uuid&facet.sort=count&_stateVer_=dbv-databases%3A18&wt=javabin&version=2: org.apache.solr.search.SyntaxError: Non-hex character in Unicode escape sequence: p
2025-12-11 15:43:16,175 [http-nio-auto-1-exec-3] ERROR c.d.c.c.c.utils.AsyncCallbackUtils - [0:0:0:0:0:0:0:1] AsyncCallback error - Request was not valid

To reproduce:

1. Store a SIARD file at a path containing a "\u" somewhere (in my example at C:\upload)
2. Open the SIARD file in DBPTK desktop

Tested on DBPTK Desktop 3.4.0

[dosubot]

Hi @seso-kdrs! I'm Dosu and I’m helping the dbptk-ui team.

The error happens because Windows file paths like C:\upload\demo.siard are sent to Solr without escaping backslashes. Solr interprets sequences like \u as the start of a Unicode escape, which fails unless followed by four hex digits, causing the syntax error you see. The DBPTK UI code passes the raw path directly into the Solr query filter, and the Solr query builder only escapes double quotes, not backslashes or other special characters. There is an escaping utility (escapeSolrSpecialChars) that handles backslashes, but it's not applied to file paths in this flow source.

A code-level fix would be to apply this escaping utility to file path values before constructing Solr queries, either in the helper that builds the filter or in the Solr query builder itself. As a workaround, avoid using \u in file paths, use forward slashes if possible, or manually escape backslashes until the code is updated.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}