stroblmeandClaude Fable 5
fea57064f9
The workflow this serves: make a venv, install what you work with, then `pip install fluksio` into the same one. Building a second environment beside it was exactly wrong — the packages the nodes need are already here, and the Modules screen was asking for them a second time. `NODE_VENV=auto` (the default) adopts that venv. It declines in the three cases where adopting would be wrong: `managed` says otherwise, a managed venv already exists and may hold packages somebody installed on purpose, or the engine is not running from a venv at all. The images set `managed`, since the venv in them holds the app and nothing of anybody else's. An adopted venv is never written to. `uv pip sync` makes a venv hold exactly the manifest, so pointed at somebody's own environment it uninstalls their work and the engine with it — `sync()` refuses outright and `reconcile()` returns before it can be called at startup, which is where that would have happened first. The Modules screen lists what is installed and drops its editor; `pip` is how that environment changes. `fluksio serve` now names the interpreter node code runs on, which is the thing a data scientist most needs to know at that moment. `fluksio-worker` already defaulted `--python` to its own interpreter, so a GPU box works the same way — that was only ever undocumented. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012ue1tkFWB1bcGy3aWhCKpU
47 lines
2.5 KiB
Python
47 lines
2.5 KiB
Python
"""Redirect the suite at its own database.
|
|
|
|
`fluksio.core.db` builds the engine at import time and several modules bind
|
|
that object, so the URL has to be in the environment before anything imports
|
|
the settings. Overriding it here — the first module pytest imports for the
|
|
package — keeps a test run from touching the development data.
|
|
|
|
A file rather than `:memory:`: the suite starts the engine's own threads (the
|
|
run service, the metrics collector, the portal connector) against this engine,
|
|
and an in-memory database is per connection unless every one of them shares a
|
|
single connection, which those threads would then contend for.
|
|
"""
|
|
|
|
import os
|
|
import tempfile
|
|
|
|
_DB_DIR = tempfile.mkdtemp(prefix="fluksio-test-")
|
|
os.environ.setdefault("DATABASE_URL", f"sqlite:///{_DB_DIR}/app_test.db")
|
|
# Nothing outside this directory: the suite must not pick up a checkout's .env
|
|
# and write into the development data.
|
|
os.environ.setdefault("FLUKSIO_ENV_FILE", os.path.join(_DB_DIR, "env"))
|
|
os.environ.setdefault("DATA_DIR", _DB_DIR)
|
|
# Named here rather than taken from a developer's .env, so the suite is the
|
|
# same run everywhere and a checkout's own superuser is never involved.
|
|
os.environ.setdefault("FIRST_SUPERUSER", "admin@example.com")
|
|
os.environ.setdefault("FIRST_SUPERUSER_PASSWORD", "testpassword")
|
|
# What `emails_enabled` needs; the tests that send mail patch SMTP_HOST on top
|
|
# of it. Nothing is delivered — the sender is faked where it matters.
|
|
os.environ.setdefault("EMAILS_FROM_EMAIL", "noreply@example.com")
|
|
# The MCP session manager can only be entered once per instance, and the suite
|
|
# builds a TestClient — and so a lifespan — per test module. Tests that want the
|
|
# endpoint mount it themselves.
|
|
os.environ["MCP_ENABLED"] = "false"
|
|
# The suite runs from a venv of its own, which "auto" would adopt as if it were
|
|
# a data scientist's — so node code would run on the checkout's environment and
|
|
# the module tests would have nothing of their own to build. The tests that
|
|
# cover adoption ask for it explicitly.
|
|
os.environ["NODE_VENV"] = "managed"
|
|
# The private seeding endpoints are opt-in; the suite is one of the two places
|
|
# (with the dev stack) where they are meant to work.
|
|
os.environ["PRIVATE_API_ENABLED"] = "true"
|
|
# The suite is the development configuration by definition: `/private` is
|
|
# gated on it (app/api/routes/private.py) and the MCP host allow-list is
|
|
# built from DOMAIN (app/mcp/http.py), while the tests speak to api.localhost.
|
|
os.environ["ENVIRONMENT"] = "local"
|
|
os.environ["DOMAIN"] = "localhost"
|