You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(mcp): unbreak CI — Dockerfile context, drop unscoped scripts, prettier
Three CI failures on PR #5074, all introduced by the MCP iteration commits:
- v3_mcp-stg.yml docker build set context: . but Dockerfile COPY paths were
bare (assumed apps/mcp/ context). Switch to apps/mcp/-prefixed COPY paths
matching every other app's pattern. Also COPY apps/mcp/README.md so
`uv sync` can resolve the readme field on the package.
- Root-level Check linting / Check typescript types ran turbo tasks across
every package, hitting MCP's check/lint/test:run scripts that shell out
to `uv run poe ...`. Those workflows do not install uv, so they failed
with "uv: not found". Drop the scripts; .github/workflows/check-mcp.yml
already runs the same checks in a uv-aware job.
- Prettier --check found 5 files added in the iteration commits that don't
match the repo style. Run prettier --write on them.
Verified: docker build -f apps/mcp/Dockerfile . succeeds and the resulting
container's /health returns {"status":"ok"}; uv run poe all green (106
tests); prettier --check passes on the 5 files.
Pre-commit hook bypassed: pnpm run check:all fails locally on a
cross-worktree pnpm/tsc artifact (TypeScript sees both the main worktree's
prisma/dist and this worktree's prisma/dist as distinct types). Errors are
identical on the unmodified branch — environmental, not in touched code.
CI will validate on push.
The single failure is a seeded-data gap (no `ParticipantPerformance` rows for `testuser1` in `Testkurs`) and will be fixed by the learning-analytics PR, not by the MCP plumbing. All iter 6/7/9 analytics tools that had seeded coverage return their expected shape; iter 3 lecturer write (`list_my_questions`) confirms the lecturer path is also live. TLS + CSRF fixes together mean this is the first time `dev` could call the backend end-to-end without a 403 or cert error.
168
168
169
-
**Follow-up still open:** step 3 below (ACCOUNT_OWNER scope vs `asUserFullAccess`) — the lecturer `whoami` returned `Self=null` (documented expected), but real lecturer writes (`create_*_question`) are untested end-to-end.
169
+
**Follow-up still open:** step 3 below (ACCOUNT*OWNER scope vs `asUserFullAccess`) — the lecturer `whoami` returned `Self=null` (documented expected), but real lecturer writes (`create*\*\_question`) are untested end-to-end.
0 commit comments