bvandeusenandClaude Opus 5.5
a706644455
CI & Build / Python lint (push) Successful in 2s
CI & Build / Build now, or wait for Android? (push) Successful in 2s
Android / Build, or is the channel already serving this? (push) Successful in 3s
Desktop (Tauri) / Build, or is the channel already serving this? (push) Successful in 2s
CI & Build / TypeScript typecheck (push) Successful in 7s
CI & Build / Python tests (push) Successful in 15s
CI & Build / integration (push) Successful in 45s
CI & Build / Build & push image (push) Skipped
Desktop (Tauri) / Windows installer (cross-compiled) (push) Successful in 4m17s
Desktop (Tauri) / Tauri desktop (Linux) (push) Successful in 7m33s
Desktop (Tauri) / Update manifest (push) Successful in 7s
Android / Kotlin + Rust (APK) (push) Successful in 11m25s
Step 2 of milestone 481. The operator chose a full rename (Scribe note 5071), so this goes past the display strings into the identities: - src/thoughtsync → src/inkwell; every import, the Dockerfile and both compose commands, alembic env, pyproject - THOUGHTSYNC_* → INKWELL_* (database URL, secret key, log level, tag/port/bind) - container data dir /var/thoughtsync → /var/inkwell - image git.fabledsword.com/bvandeusen/inkwell; Postgres user/db default inkwell; CI's integration service follows - the files the image serves are inkwell.*. fetch-clients.sh still fetches the thoughtsync-named release assets, because the lanes that publish them are renamed in steps 3 and 4 - exports are written with app "inkwell" Two deliberate exceptions, both because data rides on them: - compose volumes are now named explicitly and overridable (INKWELL_DB_VOLUME, INKWELL_DATA_VOLUME), so a deployment installed as ThoughtSync points at the volumes and DB identity it already has. .env.example says exactly what to set - import still accepts app "thoughtsync", because exports written before the rename are backups. Tested both ways Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
19 lines
737 B
Python
19 lines
737 B
Python
import uuid
|
|
|
|
from inkwell.acl import visible_to_user
|
|
from inkwell.models.user import User
|
|
|
|
|
|
def test_visible_to_user_builds_owner_or_shared_predicate():
|
|
"""DB-free smoke test: the predicate compiles and references both the direct
|
|
(shares) and group (group_members) grant paths. Functional row-visibility is
|
|
verified against a live database in M1, once notes are a real shareable
|
|
resource (family practice: DB-backed tests run against the dev image, not CI).
|
|
"""
|
|
uid = uuid.uuid4()
|
|
# User stands in as a shareable resource purely to exercise the SQL builder.
|
|
clause = visible_to_user("note", User.id, User.id, uid)
|
|
sql = str(clause).lower()
|
|
assert "shares" in sql
|
|
assert "group_members" in sql
|