Avoid duplicate service IDs during GTFS merge - #482
Conversation
Reserve source IDs and retry renamed candidates until an unused ID is found. Add regression coverage for issue OneBusAway#142. Fixes OneBusAway#142
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review. 📝 WalkthroughWalkthroughThe merge strategy now reserves source raw IDs and searches successive renamed candidates that do not collide with source or merged-output IDs. Tests cover service-calendar IDs, related references, fallback behavior, and chained collisions. ChangesService ID collision handling
Estimated code review effort: 3 (Moderate) | ~20 minutes Merge Risk: ⚪ Minimal · up to The PR prevents duplicate service IDs during GTFS merging and adds focused regression coverage for reference consistency. No actionable merge-blocking risk remains after normal checks and review. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
Summary
T0/a-T0collision reported in Merging already merged feeds may create duplicate IDs #142.Fixes #142
Testing
mvn -pl onebusaway-gtfs-merge test(18 tests passed)mvn -pl onebusaway-gtfs-merge spotless:checkgit diff --checkNote:
mvn -pl onebusaway-gtfs-merge -am testis blocked on Windows before reaching the merge module by two existingIndividualCsvEntityWriterTestLF-vs-CRLF assertions. The 14.2.3-SNAPSHOT dependencies were built with tests skipped, then the complete merge-module test suite was run successfully.Summary by CodeRabbit