Conversation
…nLake#2) - Replace local timeout variables with useRef - Clear pending timeouts in useEffect cleanup - Prevents state update on unmounted component warning Closes OpenLake#2
Prevents the solver from running indefinitely on small timeStep /
large endTime combinations. Returns { success: false, error } when
the cap is hit so the UI can surface a descriptive message.
Closes OpenLake#1
|
@mahek395 is attempting to deploy a commit to the OpenLake_Website Team on Vercel. A member of the Team first needs to authorize it. |
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 7 minutes and 20 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 participant
Problem
TransientSolver.solve() had no iteration cap — small timeStep + large endTime combinations could run millions of matrix solves, blocking the UI thread and exhausting memory.
Fix
Added a MAX_STEPS = 100_000 hard cap. When exceeded, solve() returns { success: false, error, steps } instead of hanging.
Note
TransientSolver.js was not present in the repo. Created it at lib/TransientSolver.js with the guard included from the start.
Closes #1