Fix MockRoutingService bugs: Availability, Travel Time, Distance Calculation#87
Fix MockRoutingService bugs: Availability, Travel Time, Distance Calculation#87MRiabov wants to merge 1 commit into
Conversation
…ance) - Implement iterative nearest-neighbor greedy algorithm for better spatial routing. - Add `_check_availability` to enforce CustomerAvailability constraints (wait or reject). - Fix travel time calculation unit (use km instead of meters/1000). - Fix distance calculation to use employee's current location instead of home. - Add regression test `tests/test_mock_routing_bugs.py`. Co-authored-by: MRiabov <108194191+MRiabov@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
1 participant
Fixed 3 critical bugs in
MockRoutingService:CustomerAvailabilitywindows. Added logic to wait for window start or reject if job doesn't fit.Verified with new regression tests in
tests/test_mock_routing_bugs.py.PR created automatically by Jules for task 5390812382860715750 started by @MRiabov