fuse4dbricks 0.7.0__tar.gz → 0.7.2__tar.gz

{fuse4dbricks-0.7.0 → fuse4dbricks-0.7.2}/.github/workflows/test.yml

@@ -54,7 +54,7 @@ jobs:
     - name: Build a binary wheel and a source tarball
       run: uv build
     - name: Store the distribution packages
-      uses: actions/upload-artifact@v5
+      uses: actions/upload-artifact@v7
       with:
         name: python-package-distributions
         path: dist/

{fuse4dbricks-0.7.0 → fuse4dbricks-0.7.2}/CHANGELOG.md

@@ -1,3 +1,22 @@
+# 0.7.2 (2026-06-19)
+
+- Fix a just-created file or directory being reported as nonexistent for up to
+  the negative-cache TTL (~5s) when its path had been stat'd before it existed.
+  Probing a not-yet-existing path records a negative (not-found) cache entry,
+  and `invalidate()` — called on every mutating op (create/write, `mkdir`,
+  `unlink`/`rmdir`, `rename`, truncate) — cleared the attribute and directory
+  caches but left that negative entry in place, so a subsequent `stat` kept
+  returning `ENOENT` until the entry expired. `invalidate()` now also evicts the
+  path's negative-cache entries (for every principal).
+
+# 0.7.1 (2026-06-17)
+
+- Unmount cleanly on `SIGTERM`/`SIGHUP` (e.g. `systemctl stop`). trio only turns
+  `SIGINT` (Ctrl-C) into a clean shutdown; other termination signals killed the
+  process before `pyfuse3.close()` ran, leaving the kernel with a stale mount
+  that showed up as `d?????????` in `ls`/`df`. All termination signals now run
+  the same orderly unwind that unmounts the filesystem.
+
 # 0.7.0 (2026-06-17)
 
 - Fix files written from a Windows application through WSL being uploaded at

{fuse4dbricks-0.7.0 → fuse4dbricks-0.7.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: fuse4dbricks
-Version: 0.7.0
+Version: 0.7.2
 Summary: FUSE driver for Databricks Unity Catalog Volumes.
 Project-URL: Homepage, https://github.com/zeehio/fuse4dbricks
 Author-email: Sergio Oller <sergioller@gmail.com>
@@ -261,6 +261,13 @@ user has to provide its own access token.
       User=root
       WorkingDirectory=/opt/fuse4dbricks
       ExecStart=/opt/fuse4dbricks/fuse4dbricks_start.sh
+      # On stop, fuse4dbricks catches SIGTERM and unmounts itself. Give it time
+      # to finish before systemd escalates to SIGKILL (which cannot be caught
+      # and would leave a stale mount).
+      TimeoutStopSec=30
+      # Belt-and-suspenders: if the process was hard-killed and left a stale
+      # mount, force-unmount it. '-' ignores failure when nothing is mounted.
+      ExecStopPost=-/bin/fusermount3 -uz /Volumes
       Restart=on-failure
       RestartSec=5
 
@@ -268,6 +275,10 @@ user has to provide its own access token.
       WantedBy=multi-user.target
       EOF
 
+  If your mountpoint is not `/Volumes`, update it in `ExecStopPost` to match.
+  On systems that ship FUSE 2 rather than FUSE 3, use the absolute path to
+  `fusermount` (e.g. `/usr/bin/fusermount`) instead of `fusermount3`.
+
 
 - Reload the daemon lists
 

{fuse4dbricks-0.7.0 → fuse4dbricks-0.7.2}/README.md

@@ -238,6 +238,13 @@ user has to provide its own access token.
       User=root
       WorkingDirectory=/opt/fuse4dbricks
       ExecStart=/opt/fuse4dbricks/fuse4dbricks_start.sh
+      # On stop, fuse4dbricks catches SIGTERM and unmounts itself. Give it time
+      # to finish before systemd escalates to SIGKILL (which cannot be caught
+      # and would leave a stale mount).
+      TimeoutStopSec=30
+      # Belt-and-suspenders: if the process was hard-killed and left a stale
+      # mount, force-unmount it. '-' ignores failure when nothing is mounted.
+      ExecStopPost=-/bin/fusermount3 -uz /Volumes
       Restart=on-failure
       RestartSec=5
 
@@ -245,6 +252,10 @@ user has to provide its own access token.
       WantedBy=multi-user.target
       EOF
 
+  If your mountpoint is not `/Volumes`, update it in `ExecStopPost` to match.
+  On systems that ship FUSE 2 rather than FUSE 3, use the absolute path to
+  `fusermount` (e.g. `/usr/bin/fusermount`) instead of `fusermount3`.
+
 
 - Reload the daemon lists
 

{fuse4dbricks-0.7.0 → fuse4dbricks-0.7.2}/fuse4dbricks/fs/metadata_manager.py

@@ -480,6 +480,18 @@ class MetadataManager:
             if attr_cache_key in self._attr_cache:
                 del self._attr_cache[attr_cache_key]
 
+            # A mutating op (create/write/mkdir/rename/truncate/delete) just
+            # changed this path's presence, so any cached negative is now stale.
+            # Drop it for every principal: invalidate() is synchronous and has
+            # no principal in hand, and a just-created path must be immediately
+            # visible on this mount rather than hidden until the negative TTL
+            # expires. Build the key list first, then delete -- there is no
+            # await between, so this stays atomic under trio (mirrors the
+            # lock-free contract of the rest of this method).
+            stale_negatives = [k for k in self._negative_cache if k[1] == fs_path]
+            for key in stale_negatives:
+                del self._negative_cache[key]
+
             parent_path = "/".join(fs_path.rstrip("/").split("/")[:-1]) or "/"
             if parent_path in self._dir_cache:
                 del self._dir_cache[parent_path]

{fuse4dbricks-0.7.0 → fuse4dbricks-0.7.2}/fuse4dbricks/main.py

@@ -2,6 +2,7 @@
 import argparse
 import logging
 import os
+import signal
 import traceback
 import sys
 
@@ -145,6 +146,26 @@ def setup_logging(debug_mode):
         logging.getLogger("pyfuse3").setLevel(logging.INFO)
 
 
+async def _shutdown_on_signal(cancel_scope: trio.CancelScope):
+    """Translate termination signals into a clean trio shutdown.
+
+    Without this, trio only converts SIGINT (Ctrl-C) into a KeyboardInterrupt;
+    SIGTERM (e.g. ``systemctl stop``) and SIGHUP kill the process outright, so
+    ``start_fuse``'s ``finally`` never runs and ``pyfuse3.close()`` never gets
+    a chance to unmount. The kernel is then left with a stale mount that shows
+    up as ``d?????????`` in ``ls``/``df``. Cancelling the nursery here makes
+    every signal follow the same orderly unwind that unmounts the filesystem.
+    """
+    with trio.open_signal_receiver(signal.SIGTERM, signal.SIGINT, signal.SIGHUP) as signals:
+        async for signum in signals:
+            logging.info(
+                "Received %s, unmounting and shutting down...",
+                signal.Signals(signum).name,
+            )
+            cancel_scope.cancel()
+            return
+
+
 async def start_fuse(ops, mountpoint, allow_other, debug_mode, stopped_evt: trio.Event | None = None):
     mount_options = ["fsname=fuse4dbricks", "noatime"]
     if allow_other:
@@ -165,7 +186,7 @@ async def start_fuse(ops, mountpoint, allow_other, debug_mode, stopped_evt: trio
         pass
     finally:
         try:
-            pyfuse3.close()
+            pyfuse3.close(unmount=True)
         finally:
             if stopped_evt is not None:
                 stopped_evt.set()
@@ -251,6 +272,7 @@ async def async_main():
         async with trio.open_nursery() as nursery:
             persistence.run_services(nursery)
             data_manager.run_services(nursery)
+            nursery.start_soon(_shutdown_on_signal, nursery.cancel_scope)
             nursery.start_soon(start_fuse, operations, mountpoint, args.allow_other, args.debug, stopped_evt)
 
             await stopped_evt.wait()

{fuse4dbricks-0.7.0 → fuse4dbricks-0.7.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "fuse4dbricks"
-version = "0.7.0"
+version = "0.7.2"
 description = "FUSE driver for Databricks Unity Catalog Volumes."
 readme = "README.md"
 requires-python = ">=3.11"

{fuse4dbricks-0.7.0 → fuse4dbricks-0.7.2}/tests/test_metadata_manager.py

@@ -453,6 +453,26 @@ def test_invalidate_nonexistent_path_does_not_raise(manager):
     manager.invalidate("/nonexistent/path/file.txt", is_dir=False)  # Must not raise
 
 
+def test_invalidate_clears_negative_cache_for_all_principals(manager, ctx):
+    """A mutating op (create/write/mkdir/...) routes through invalidate(); it
+    must drop the path's negative entry for EVERY principal so a just-created
+    file is immediately visible instead of hidden until the negative TTL
+    expires. This is the negative-cache poisoning bug: stat a path before it
+    exists, create it, then stat again -> stale ENOENT for ~ttl_negative."""
+    future = time.time() + 100
+    fs_path = "/cat/sch/vol/file.txt"
+    manager._negative_cache[("alice@example.com", fs_path)] = future
+    manager._negative_cache[("bob@example.com", fs_path)] = future
+    # A negative for a *different* path must survive.
+    manager._negative_cache[("alice@example.com", "/cat/sch/vol/other.txt")] = future
+
+    manager.invalidate(fs_path, is_dir=False)
+
+    assert ("alice@example.com", fs_path) not in manager._negative_cache
+    assert ("bob@example.com", fs_path) not in manager._negative_cache
+    assert ("alice@example.com", "/cat/sch/vol/other.txt") in manager._negative_cache
+
+
 # ---------------------------------------------------------------------------
 # reauthorize  (token change -> refresh the uid -> principal mapping)
 # ---------------------------------------------------------------------------

{fuse4dbricks-0.7.0 → fuse4dbricks-0.7.2}/uv.lock

@@ -353,7 +353,7 @@ wheels = [
 
 [[package]]
 name = "fuse4dbricks"
-version = "0.6.2"
+version = "0.7.2"
 source = { editable = "." }
 dependencies = [
     { name = "databricks-sdk" },