fix: engine delegates to tracker.getNextTask() for dependency ordering#116
fix: engine delegates to tracker.getNextTask() for dependency ordering#116
Conversation
The PR #109 fix added getNextTask() to BeadsTrackerPlugin but the engine never called it. The engine was doing its own getTasks() + isTaskReady() loop which returned tasks in wrong order since bd list doesn't include dependency data. Changes: - Add excludeIds to TaskFilter for skipped task handling - Update engine's getNextAvailableTask() to delegate to tracker.getNextTask() - Add tests for delegation and excludeIds filter Fixes #97
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
|
Warning Rate limit exceeded
⌛ 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. 📒 Files selected for processing (7)
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 |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #116 +/- ##
==========================================
+ Coverage 41.58% 41.61% +0.02%
==========================================
Files 57 57
Lines 12600 12606 +6
==========================================
+ Hits 5240 5246 +6
Misses 7360 7360
🚀 New features to boost your workflow:
|
fix: engine delegates to tracker.getNextTask() for dependency ordering
Summary
tracker.getNextTask()instead of doing its own task selection loopexcludeIdstoTaskFilterfor skipped task handlinggetNextTask()toBeadsTrackerPluginbut the engine never called itRoot Cause
The engine's
getNextAvailableTask()was doing its own loop:getTasks()(returns tasks in reverse ID order from beads)isTaskReady()on eachThis bypassed the
getNextTask()method that usesbd readyfor proper dependency ordering.Changes
excludeIdstoTaskFilterexcludeIdsinfilterTasks()getNextTask()tracker.getNextTask()withexcludeIdsTest plan
bun run typecheckpassesbun run buildpassesbun testpasses (993 pass, 7 todo, 0 fail)Fixes #97