Remember the last node extraction after a restart - #6
Conversation
Rare ore cycles were depositing niter and arcane crystals, but the last-cycle line lived only in memory and came back as Extracted: Nothing after a restart. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (4)
Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review. 📝 WalkthroughWalkthroughThe change adds JSON conversion for node last-cycle results and uses it when loading and saving nodes. It also adds tests for conversion and numeric parsing, plus JUnit Jupiter and Maven Surefire configuration. ChangesLast-cycle result persistence
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Bug fix Suggested reviewers: Merge Risk: ⚪ Minimal · up to Saved extraction results remain visible after a normal restart. No issue identified here needs resolution before merging. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 9 functions across 3 files. (1 skipped: 1 unsupported.)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
A rabbit checks the saved result, Comment |
Summary
Extracted: Nothinguntil the next multi-hour output.Test plan
mvn testcovers round-tripping niter and arcane crystal counts, including the numeric types the JSON parser writesMade with Cursor
Summary by CodeRabbit
New Features
Tests