Fix GraalVM 21 compatibility for multi-isolate usage

Signed-off-by: Avelino <31996+avelino@users.noreply.github.com>

Author: avelino

bindings/rust/src/lib.rs

@@ -706,8 +706,13 @@ mod tests {
         // But we verify that IF it fails, it's with an expected error type
         if let Err(err) = result {
             match err {
-                ChronDBError::SetupFailed(_) | ChronDBError::IsolateCreationFailed => {
-                    // Expected error types when library is not found or fails to load
+                ChronDBError::SetupFailed(_)
+                | ChronDBError::IsolateCreationFailed
+                | ChronDBError::OpenFailed(_) => {
+                    // Expected error types:
+                    // - SetupFailed: library not found
+                    // - IsolateCreationFailed: GraalVM isolate couldn't be created
+                    // - OpenFailed: library found but database open failed (e.g., path issues)
                 }
                 other => panic!("Unexpected error type: {}", other),
             }
@@ -824,6 +829,13 @@ mod tests {
             // db drops here, simulating process exit
         }
 
+        // Remove stale Lucene lock (cleanup code uses lsof which doesn't work
+        // when the same process creates multiple GraalVM isolates)
+        let lock_file = std::path::Path::new(index_str).join("write.lock");
+        if lock_file.exists() {
+            let _ = std::fs::remove_file(&lock_file);
+        }
+
         // === Second "process" - reopen and verify ===
         {
             let db = ChronDB::open(data_str, index_str)

src/chrondb/util/locks.clj

@@ -15,8 +15,9 @@
   (let [dir-file (io/file dir)]
     (when (.exists dir-file)
       (->> (file-seq dir-file)
-           (filter #(and (.isFile %)
-                         (.endsWith (.getName %) ".lock")))))))
+           (filter (fn [^java.io.File f]
+                     (and (.isFile f)
+                          (.endsWith (.getName f) ".lock"))))))))
 
 (defn stale-lock?
   "Returns true if the lock file is older than the stale timeout.