6 Commits

Include renames

Author	SHA1	Message	Date
woggioni	f59064e580	Upgrade kaya to 0.0.7	2026-10-01 23:43:55 +08:00
woggioni	5eccaafadc	Upgrade kaya to 0.0.6 ... kaya-oidc 0.0.6 namespaces its session state per provider as oidc:{provider}:user (the default provider is "default", so the key is oidc:default:user). The unprefixed oidc_user key is no longer written: left unadapted, every websocket upgrade would be rejected with 401 and traced requests would silently lose their user.id attribute. Adopt it with a session_user helper on tavolo.platform.auth that finds any provider's user, used by both get_ws_user and telemetry's session_tag_hook. Websocket and route handlers keep their signatures. kaya-otel 0.0.6 only enriches websocket spans with standard URL, network and peer attributes (plus error.type), which needs no application change. Regenerate the lock: the eight kaya pins move to 0.0.6 and, the wheels' declared metadata being unchanged, nothing else moves. tavolo-platform now floors kaya-core>=0.0.6 (it reads the new session layout) and tavolo-app floors kaya-otel>=0.0.6. As kaya documents, the session-key move signs existing logged-in users out once; they simply log in again.	2026-10-01 20:38:21 +08:00
woggioni	723b3b11cf	Upgrade kaya to 0.0.5 ... kaya 0.0.5 surfaces a vanished websocket peer as kaya.core.WebSocketDisconnect instead of leaking granian's RSGIProtocolClosed: receive() reports a close message so iteration ends normally, sends raise the new exception, and KayaApp.handle_websocket swallows it as normal termination. Adopt it: drop the granian-specific workaround from the platform websocket handler, catch WebSocketDisconnect in the send helper, and model the new semantics in the abrupt-disconnect test (with coverage that a send on a vanished peer is ignored). Regenerate the lock: the eight kaya pins move to 0.0.5 (declared metadata is unchanged) and pip-compile also bumps PyJWT to 2.15.1, a security release with no breaking changes for kaya-oidc's jwt.decode usage. tavolo-platform now floors kaya-core>=0.0.5 (it imports WebSocketDisconnect) and tavolo-app floors kaya-otel>=0.0.5.	2026-09-30 06:38:02 +08:00
woggioni	a3e8ff3206	Trace Postgres and Redis queries with the contrib instrumentations ... Builds the TracerProvider in tavolo.telemetry (kaya-otel's is private) and injects it into kaya-otel, then instruments asyncpg and redis through opentelemetry-instrumentation-asyncpg/redis. Redis command values are redacted and asyncpg spans carry the parameterized SQL only.	2026-09-28 03:38:59 +08:00
woggioni	98d4485375	Export app, process and log telemetry when OTEL_ENABLED is set ... Adds tavolo.active_users and tavolo.ongoing_games gauges, process/CPython metrics via opentelemetry-instrumentation-system-metrics and OTLP log export. The game store tracks ongoing matches (Redis sorted set, in-memory set) and the session stores expose live counts for the gauges; a poller refreshes them since metric callbacks cannot await the stores.	2026-09-28 03:38:59 +08:00
woggioni	2b738ea2fe	Move tavolo-app under packages/ for a uniform monorepo layout ... Relocate the composition root (app, config, static, logging_config, aerich_config) from server/src/tavolo/ to packages/tavolo-app/src/tavolo/, with its own pyproject.toml and README like the sibling distributions. Module paths and the granian entrypoint are unchanged. server/pyproject.toml remains as a tooling shim ([tool.aerich] next to ./migrations, [tool.mypy] for runs from server/); the Dockerfile installs all three distributions from ./packages. Verified: all suites green, mypy clean per package, aerich resolves the moved config identically, wheel builds.	2026-09-21 13:04:09 +08:00