Files
zeekay 1b367e2b62 chore: rebase the tree onto upstream master
The tree was a debranded snapshot of upstream taken around 2026-02-20, and
upstream has moved about five months since. This replaces it with upstream
master, mechanically re-derived: bin/debrand does the rename, and the
pipeline and squashed migrations are restored from the shipped tree.

Not a merge. The previous import replaced the tree wholesale in a single
commit, so there is no shared content history to merge against. Reproducing
the rename on the new tree is what actually converges.

What survives: .hanzo/workflows, the Dockerfiles and bin/docker* entrypoints,
compose files, LLM.md, and insights/migrations. The squashed initial
migration is load-bearing — the live database records it by name, so
upstream's ~918 individual migrations cannot come back.

Nine products are dropped as unreferenced. Twenty-one more that we do not run
are kept anyway because the core app still imports them; unpicking those is a
refactor and does not belong in a rebase.

This base does not build yet, and the reasons are not in the rename:
upstream now wants Python 3.13.13 against our 3.12.12 and Django 5.2 against
our 4.2, and the dependency manifests still name upstream packages that we
republish under our own names. Those are decisions, not renames.
2026-08-01 15:44:40 -07:00

58 lines
1.9 KiB
Python

"""Test-suite fixtures for the signals backend.
`_scout_team_scope` auto-wraps every test that has a `self.team` (i.e. is built
on `BaseTest`/`APIBaseTest`) in `team_scope(self.team.id)`. The scout models
(`SignalScoutConfig`, `SignalScoutRun`, `SignalScratchpad`) use
`TeamScopedRootMixin`, so their default `.objects` manager is fail-closed and
raises `TeamScopeError` when called outside a team context. Test setUp / body
code that does `Model.objects.create(...)` directly (without going through a
DRF request that sets context via `TeamAndOrgViewSetMixin.initial`) would
otherwise need an explicit `with team_scope(...)` wrapper everywhere.
The fixture is a no-op for tests that don't have a `team` attribute (pure unit
tests, async harness tests with their own setup) — those keep working unchanged.
The fixture is also harmless for non-scout tests in this directory: the older
`Signal*` models don't read the ContextVar.
"""
from __future__ import annotations
import random
import pytest
import pytest_asyncio
from asgiref.sync import sync_to_async
from insights.models import Organization, Team
from insights.models.scoping import team_scope
@pytest.fixture(autouse=True)
def _scout_team_scope(request: pytest.FixtureRequest):
instance = getattr(request, "instance", None)
if instance is None or not hasattr(instance, "team") or instance.team is None:
yield
return
with team_scope(instance.team.id):
yield
@pytest_asyncio.fixture
async def aorganization():
organization = await sync_to_async(Organization.objects.create)(
name=f"SignalsTelemetryOrg-{random.randint(1, 99999)}",
)
yield organization
await sync_to_async(organization.delete)()
@pytest_asyncio.fixture
async def ateam(aorganization):
team = await sync_to_async(Team.objects.create)(
organization=aorganization,
name=f"SignalsTelemetryTeam-{random.randint(1, 99999)}",
)
yield team
await sync_to_async(team.delete)()