letify 2.6.0__tar.gz → 2.6.1__tar.gz

{letify-2.6.0 → letify-2.6.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: letify
-Version: 2.6.0
+Version: 2.6.1
 Summary: Declarations that become infrastructure.
 Project-URL: Homepage, https://github.com/DarkPyonix/letify
 Project-URL: Documentation, https://github.com/DarkPyonix/letify/tree/main/docs

{letify-2.6.0 → letify-2.6.1}/docs/SPEC.md

@@ -1498,6 +1498,8 @@ For an ephemeral provider that archives its environment, the default managed Pyt
 
 Otherwise the sync step sets `UV_CACHE_DIR`, `UV_PYTHON_INSTALL_DIR` and `UV_TOOL_DIR` under `<workspace root>` for `uv sync` and `uv pip install`, unconditionally: not only when the provider's `persistence` is `persistent`, and not only when it sets no `env_root`. An `Env.vars` entry naming one of the three wins over this rule for that variable.
 
+`UV_PYTHON_INSTALL_DIR` is the exception: it follows the project directory whenever the provider sets an `env_root`, because the interpreter belongs with the `.venv` it serves and a workspace root is not always a filesystem one can be unpacked on. Modal's workspace root is a Modal volume, measured as supporting no hard link at all: a link inside it fails with `EPERM` and a link from it to the sandbox disk with `EXDEV`. So `uv sync --python 3.13` on a sandbox whose image carries 3.12 downloaded a managed interpreter into the volume and failed with `error: Operation not permitted (os error 1)`, which named neither the directory nor the reason. The archive case already placed it there, for its own reason, so this makes the two agree.
+
 On a runtime with a persistent workspace root the cache outlives a container rebuild along with the projects built from it. On an ephemeral provider the cache is filled once per runtime wherever it lives and discarded with it, but it is still written under the workspace root rather than the home directory, because the workspace root may be the only writable path.
 
 letify never deletes from the cache. The first sync on a runtime fills `<workspace root>/uv-cache` once, and a cache uv already had elsewhere is left in place. `uv cache prune` run with the same `UV_CACHE_DIR` removes entries no lock file needs any more; a file still hard linked from a `.venv` keeps its disk blocks until that `.venv` is removed as well.

{letify-2.6.0 → letify-2.6.1}/letify/__init__.py

@@ -66,7 +66,7 @@ distributed: Final = Host.distributed
 # The enum class stays importable from letify.declare.instance for letify's own use.
 del Host
 
-__version__ = "2.6.0"
+__version__ = "2.6.1"
 
 
 def fetch(tensor):  # type: ignore[no-untyped-def]

{letify-2.6.0 → letify-2.6.1}/letify/runtime/bootstrap.py

@@ -357,7 +357,9 @@ def sync_source(
     It raises ``RuntimeError`` with ``uv could not be installed on <name>`` or ``uv sync
     failed on <name>`` so the local side can name the step that failed.
     """
-    root = root or project_dir(DEFAULT_WORKSPACE_ROOT, env)
+    # Derived from the workspace root when it is given, so the two cannot disagree: the
+    # managed Python's directory is chosen by whether the project lies inside it.
+    root = root or project_dir(workspace or DEFAULT_WORKSPACE_ROOT, env)
     workspace = workspace or DEFAULT_WORKSPACE_ROOT
     encoded = {key: base64.b64encode(value).decode() for key, value in files.items()}
     sync_args = sync_command(env)[1:]
@@ -400,8 +402,15 @@ def sync_source(
     ]
     declared = dict(env.variables)
     directories = uv_env(workspace)
-    if archive:
-        # Keep an interpreter uv downloads inside the tree sent to the next VM.
+    inside = root.rstrip("/") == workspace.rstrip("/") or root.startswith(
+        workspace.rstrip("/") + "/"
+    )
+    if archive or not inside:
+        # Keep an interpreter uv downloads inside the tree sent to the next VM, and, when
+        # the project directory is off the workspace root, beside the .venv it serves: a
+        # workspace root is not always a filesystem an interpreter can be unpacked on.
+        # Spec "Remote paths letify writes": Modal's is a volume that carries no hard
+        # link, so unpacking one there fails with Operation not permitted.
         directories["UV_PYTHON_INSTALL_DIR"] = f"{root.rstrip('/')}/.letify-python"
     for key, value in directories.items():
         if key not in declared:

{letify-2.6.0 → letify-2.6.1}/letify-core/Cargo.lock

@@ -138,7 +138,7 @@ dependencies = [
 
 [[package]]
 name = "letify-agent"
-version = "2.6.0"
+version = "2.6.1"
 dependencies = [
  "letify-wire",
  "libloading",
@@ -146,7 +146,7 @@ dependencies = [
 
 [[package]]
 name = "letify-driver"
-version = "2.6.0"
+version = "2.6.1"
 dependencies = [
  "letify-wire",
 ]
@@ -164,7 +164,7 @@ dependencies = [
 
 [[package]]
 name = "letify-wire"
-version = "2.6.0"
+version = "2.6.1"
 
 [[package]]
 name = "libc"

{letify-2.6.0 → letify-2.6.1}/letify-core/Cargo.toml

@@ -8,7 +8,7 @@ resolver = "3"
 members = ["letify-wire", "letify-driver", "letify-agent", "letify-quic"]
 
 [workspace.package]
-version = "2.6.0"
+version = "2.6.1"
 edition = "2024"
 license = "MIT"
 repository = "https://github.com/DarkPyonix/letify"

{letify-2.6.0 → letify-2.6.1}/letify-ext/package-lock.json

@@ -1,12 +1,12 @@
 {
   "name": "letify-status",
-  "version": "2.6.0",
+  "version": "2.6.1",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "letify-status",
-      "version": "2.6.0",
+      "version": "2.6.1",
       "license": "SEE LICENSE IN LICENSE",
       "devDependencies": {
         "@types/node": "^18.19.0",

{letify-2.6.0 → letify-2.6.1}/letify-ext/package.json

@@ -2,7 +2,7 @@
   "name": "letify-status",
   "displayName": "letify Status",
   "description": "letify quota and GPU activity in the status bar, read from the letify CLI.",
-  "version": "2.6.0",
+  "version": "2.6.1",
   "publisher": "darkpyonix",
   "license": "SEE LICENSE IN LICENSE",
   "repository": {

{letify-2.6.0 → letify-2.6.1}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "letify"
-version = "2.6.0"
+version = "2.6.1"
 description = "Declarations that become infrastructure."
 readme = "README.md"
 requires-python = ">=3.11"

{letify-2.6.0 → letify-2.6.1}/tests/test_runtime.py

@@ -2523,3 +2523,44 @@ def test_a_lock_naming_cloudpickle_alone_is_accepted(tmp_path) -> None:
     (tmp_path / "uv.lock").write_text('version = 1\n\n[[package]]\nname = "cloudpickle"\n')
     files = bootstrap.project_files(Env(lock=str(tmp_path / "uv.lock")))
     assert b"cloudpickle" in files["uv.lock"]
+
+
+def test_the_managed_python_goes_with_the_venv_when_the_provider_sets_an_env_root() -> None:
+    """Spec "Remote paths letify writes": a workspace root is not always unpackable.
+
+    Modal's workspace root is a Modal volume, which supports no hard link at all: a link
+    inside it fails with EPERM and one to the sandbox disk with EXDEV. So uv downloading a
+    managed interpreter into it failed with "Operation not permitted (os error 1)", naming
+    neither the directory nor the reason. Reproduced on a live Modal T4 sandbox: the same
+    sync with that directory on the sandbox disk succeeds.
+    """
+    from letify.declare.env import Env
+    from letify.runtime import bootstrap
+
+    env = Env()
+    project = "/root/.letify-env/project/abc123"
+    files = {"pyproject.toml": b"[project]\n", "uv.lock": b""}
+    # A persistent provider archives nothing, which is the path that was left on the volume.
+    source = bootstrap.sync_source(
+        env, files, root=project, name="sandbox", workspace="/letify", archive=False
+    )
+    assert f"UV_PYTHON_INSTALL_DIR'] = os.path.expanduser('{project}/.letify-python')" in source
+    # The cache and the tool directory stay on the workspace root, which outlives a sandbox
+    # and was measured to carry them.
+    assert "UV_CACHE_DIR'] = os.path.expanduser('/letify/uv-cache')" in source
+    assert "UV_TOOL_DIR'] = os.path.expanduser('/letify/uv-tool')" in source
+
+
+def test_the_managed_python_stays_on_the_workspace_root_without_an_env_root() -> None:
+    """Spec "Remote paths letify writes": the workspace root is the only writable path
+    some accounts have, so nothing moves where the venv is already under it."""
+    from letify.declare.env import Env
+    from letify.runtime import bootstrap
+
+    env = Env()
+    project = "/workspace/project/abc123"
+    files = {"pyproject.toml": b"[project]\n", "uv.lock": b""}
+    source = bootstrap.sync_source(
+        env, files, root=project, name="lab", workspace="/workspace", archive=False
+    )
+    assert "UV_PYTHON_INSTALL_DIR'] = os.path.expanduser('/workspace/uv-python')" in source