Repository navigation
Don't skip scheduled moves while a parity check is paused - #268
Conversation
A paused check, rebuild or clear keeps mdResyncPos above 0, so with either parity option on No every scheduled run was skipped until the check was resumed or cancelled. Both gates now read mdResync, which is 0 while paused.
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 55 minutes. View limit details
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
|
@coderabbitai full review |
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 0 |
| Duplication | 0 |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
Action not completed
|
A paused check, rebuild or clear keeps
mdResyncPosabove 0, so with either "run during a parity check / rebuild" option on No, every scheduled run was skipped until the check was resumed or cancelled.mover.php: both gates count a check as running only whilemdResyncis above 0, the value Unraid's Pause/Resume button reads.Summary by CodeRabbit