Repository navigation
fix: resolve libsql wal conflict auto-healing and reports hook order - #11
Merged
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📋 Summary of Changes
src/lib/db.ts):globalDbUrlcaching so connection instances are properly reused across requests instead of repeatedly destroyed and re-opened.handleWalConflict()to safely close dangling handles, unlink conflicted/diverged local replica files, pull a clean replica from Turso, and auto-retry write queries.src/app/api/auth/otp/verify/route.ts):secure: trueon cookies so localhost (127.0.0.1/localhost) does not reject session cookies overhttp://.src/app/reports/page.tsx):useMemoat line 539 (which was invoked after early returns on loading and error states) with direct calculation. All hooks inReportsPagenow execute unconditionally at top-level.🎯 Target Branch Verification
stagingbranch (Direct PRs tomainare reserved exclusively for staging-to-main production releases).🔍 Context & Motivation
WalConflicterrors during OTP send/writes on embedded replica.React has detected a change in the order of Hooks called by ReportsPageand runtime errorRendered more hooks than during the previous render.✅ Verification & Quality Checklist
npx tsc --noEmitpasses with 0 errors.npm testpasses 70/70 tests.npm run buildsucceeds cleanly.