Fix guitar bend hold line assert during writeProperties - #34628
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan includes up to 10 reviews per rolling hour; 9 remain after this review. 📝 WalkthroughWalkthrough
Merge Risk: ⚪ Minimal · up to This localized change stops invalid hold-line endpoints from being written while preserving other hold-line properties; no actionable merge-blocking risk remains after normal checks and review. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Warning Review ran into problems🔥 ProblemsLinked repositories: Public OSS repositories can only analyze public repositories installed in this organization. No linked repositories were analyzed; skipped 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 |
Inserting a
GuitarBendHoldline and saving was triggering theendElEID.isValid()assert inTWrite::writeProperties(const Spanner*...).The
GuitarBendHoldis written nested inside its parentGuitarBend, while its end element lies after the bend, on a note that may or may not have been written yet and so may have no EID assigned.Since the start and end elements of hold lines are recomputed during
GuitarBend::updateHoldLine(), I have simply stopped writing these two values to the mscx - the read values weren't actually used anyway. Other properties of the hold line are still written.