Deploy b0f223b

Merge pull request #44 from WINTER4000/chore/stale-comments-and-log-timeout

Source: https://github.com/WINTER4000/turingDNA/commit/b0f223b1eb9559ffc79c72b484b7ff98e6dbdce5

dee/auth.py

@@ -660,8 +660,9 @@ def _next_month_start_iso() -> str:
 def increment_anon_runs_on_response(response: Response) -> Response:
     """Called from inside a /api/run handler that has decided to start a
     pipeline FOR an anonymous user. Stamps the first_at timestamp on the
-    cookie if this is their first run; otherwise just bumps the
-    informational run count without resetting the trial timer.
+    cookie if this is their first run, and bumps the run count — which is
+    now the thing the gate actually reads, rather than an informational
+    counter beside a timer.
 
     Idempotent against being called twice on the same request — the
     response cookie just gets overwritten with the same data.
@@ -676,9 +677,9 @@ def increment_anon_runs_on_response(response: Response) -> Response:
     _set_anon_cookie(response, first_at, runs)
 
     # Also surface the trial state in a custom response header so the
-    # frontend can read it without parsing the cookie itself. The frontend
-    # uses this to start its own client-side countdown to the in-session
-    # "sign in to keep going" modal.
+    # frontend can read it without parsing the cookie itself. It shows the
+    # "sign in to keep going" modal when the count reaches zero. It used to
+    # arm a setTimeout here instead, which is what cut people off mid-read.
     response.headers["X-TD-Trial-Runs-Left"]  = str(max(0, ANON_FREE_RUNS - runs))
     response.headers["X-TD-Trial-Runs-Total"] = str(ANON_FREE_RUNS)
     # Kept for a client cached from before the switch: a stale auth.js still

dee/server.py

@@ -1299,10 +1299,12 @@ def create_app() -> Flask:
 
     @app.post("/api/run")
     def start_run() -> Response:
-        # Auth-or-quota gate. Anonymous users get one free run; after
-        # that this returns a 402 with kind="auth_required" and the
-        # frontend pops the sign-up gate. Signed-in users (valid Supabase
-        # JWT in Authorization header) bypass entirely.
+        # Auth-or-quota gate. Anonymous visitors get ANON_FREE_RUNS of
+        # them — runs, not minutes; see dee/auth.py for why the clock was
+        # the wrong unit. After that this returns a 402 with
+        # kind="auth_required" and the frontend pops the sign-up gate.
+        # Signed-in users (valid Supabase JWT in Authorization header)
+        # bypass entirely.
         gate = _auth.require_auth_or_quota()
         if gate is not None:
             return gate

tests/conftest.py

@@ -49,3 +49,29 @@ def _no_leaked_resolutions():
     _rc.clear()
     yield
     _rc.clear()
+
+
+@pytest.fixture(autouse=True)
+def _no_leaked_scorers():
+    """Third instance of the same hazard, and the one that actually bit.
+
+    scoring._SCORER_CACHE is process-global on purpose: ESM-2 weights load
+    once and every caller reuses them. tests/test_scoring.py already cleared
+    it around each of its own tests — but an autouse fixture declared in a
+    test module covers only that module, so every other file ran unguarded.
+
+    test_model_choice.py::test_get_scorer_never_loads_a_gpu_model_in_process
+    installs a _FakeScorer and asserts a 'small' request constructs exactly
+    one. Run alone it passes; run after anything that has already warmed the
+    cache it gets the earlier scorer back, builds nothing, and fails
+    `assert len(built) == 1` with 0. The test is also the mirror image of the
+    problem — it leaves its _FakeScorer in the cache for whatever runs next.
+
+    An order-dependent failure in the suite that gates deploys is worse than
+    the bug it hides: it fails on an unrelated commit and gets re-run until
+    it passes.
+    """
+    from dee.core import scoring as _sc
+    _sc._SCORER_CACHE.clear()
+    yield
+    _sc._SCORER_CACHE.clear()