fix: activeRundown handling#310
Conversation
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ 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 (3)
WalkthroughThis PR adds rundown-aware priority calculation to the package manager. The ChangesRundown-based expectation prioritization
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@apps/package-manager/packages/generic/src/packageManager.ts`:
- Around line 1207-1209: Add a short comment above the optional property
declaration rundownId in packageManager.ts explaining its contract with Core:
state that this field is expected to be populated by sofie-core’s expected
package data and that package-manager treats it as optional (handled in
expectations.ts for priority calculation) so missing values are allowed;
reference the expectations.ts logic in the comment to guide maintainers to where
the runtime behavior is enforced.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: e3f930b8-3199-4c85-9339-c3a491068e76
📒 Files selected for processing (3)
apps/package-manager/packages/generic/src/fakeCore.tsapps/package-manager/packages/generic/src/generateExpectations/nrk/expectations.tsapps/package-manager/packages/generic/src/packageManager.ts
2040cc7 to
b2a664d
Compare
|



About Me
This pull request is posted on behalf of the BBC
Type of Contribution
This is a: Bug fix
New Behavior
Fixes the activeRundown handling, which was discovered to be broken by #285
This has to rely on some hope of types aligning, as it appears that the types between sofie-core and package-manager are not shared in a way that makes it simple to share this property definition
Testing Instructions
Other Information
Status