fix: longer waiting for tiles#43
Conversation
|
Warning Review limit reached
More reviews will be available in 32 minutes and 41 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, 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 include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe PR improves the "My Location" button test by adding an explicit wait for the Leaflet fly-to zoom animation to complete. The test now uses ChangesMy Location Test Animation Wait
Possibly related PRs
Poem
🎯 1 (Trivial) | ⏱️ ~3 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 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 `@tests/basic/test_go_to_my_location.py`:
- Around line 42-46: The current single wait using
page.wait_for_function("!document.querySelector('.leaflet-zoom-anim')",
timeout=15000) can pass immediately if the animation element is added after the
check; change to a two-phase sync: after triggering the flyTo, first wait for
the animation to start by waiting for
document.querySelector('.leaflet-zoom-anim') to be truthy (short timeout e.g.
1–2s) using page.wait_for_function, then wait for it to disappear using the
existing wait_for_function that checks for its absence (longer timeout).
Alternatively, replace the two-phase approach with an event-based wait by
injecting a page.evaluate that attaches to the Leaflet map and resolves on the
'moveend' or 'zoomend' event (listen for 'moveend'/'zoomend') and await that
promise instead of the single-selector check.
🪄 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: 2db3f7db-50fe-49eb-a3d1-5f3c1e50c280
📒 Files selected for processing (1)
tests/basic/test_go_to_my_location.py
🧪 E2E Test Results📊 View full workflow run 📊 E2E Stress Test Performance✅ Status: PASSED (12315.03ms max < 25000ms limit)
📈 Individual Run Times
|
🧪 E2E Test Results📊 View full workflow run
|
🧪 E2E Test Results📊 View full workflow run 📊 E2E Stress Test Performance✅ Status: PASSED (13251.74ms max < 25000ms limit)
📈 Individual Run Times
|
Summary by CodeRabbit