fix(local-coding): count only new sync dates#1531
Conversation
|
@eshaanag is attempting to deploy a commit to the PRIYANSHU DOSHI's projects Team on Vercel. A member of the Team first needs to authorize it. |
GSSoC Label Checklist 🏷️@Priyanshu-byte-coder — please apply the appropriate labels before merging: Difficulty (pick one):
Quality (optional):
Validation (required to score):
|
315fa9f to
86091d0
Compare
|
Rebased this branch onto current main and pushed a follow-up after checking the failed Playwright report. The local-coding fix is still the core change, and the extra CI fixes cover the standalone E2E server missing static assets plus dashboard/public-profile auth edge cases that were breaking the smoke suite. Local validation is green: lint, type-check, the local-coding sync regression test, Node 20 production build, and the full Playwright suite. |
7cb68ee to
c0bf384
Compare
15d45c4 to
a0a019f
Compare
Summary
MAX_SESSIONS_PER_USER.Why
This fixes #1530 as part of GSSoC 2026. The sync route was adding the full incoming session count to the user's existing row count before enforcing the cap, but the database upserts by
(user_id, date). That meant normal re-syncs of existing dates could be rejected even though they would not create new rows.Testing
npm run test -- test/local-coding-sync.test.tsnpm run lintnpm run type-checknode scripts/check-deps.jsnpm ci --dry-runnpx -p node@20 -c 'node -v && npm run build'Note: the Node 20 build completed successfully. Next.js still prints the existing upstream
package-lock.jsonparse warning from conflict markers, but this PR does not touch the lockfile.Closes #1530