This repository was archived by the owner on Oct 7, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 128
Count up and restart on repeated spinnable check failures #1034
Merged
Merged
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
8809587
count up and restart on repeated spinnable check failures
crhbetz 84f4d9f
rework spinnable checking
crhbetz 90e0cb5
fix W504
crhbetz d5e741d
ensure fresh data for spinnable check, better log
crhbetz 47d44ff
timeout fetching new data is also a data failure
crhbetz 86b8959
spinnable_data_failure logic fix
crhbetz 139632a
count up and restart on repeated spinnable check failures
crhbetz 7a54645
rework spinnable checking
crhbetz fc8eb3e
fix W504
crhbetz b415a7b
ensure fresh data for spinnable check, better log
crhbetz f5ac455
timeout fetching new data is also a data failure
crhbetz c2f37cd
spinnable_data_failure logic fix
crhbetz 22cda69
Merge branch 'spinnable-data-failure' of https://github.com/crhbetz/M…
crhbetz File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This might be the culprit.
We are looping over all pokestops and gyms we found in the GMO, but if we find a gym close by, we try and delete the pokestop at that location, and claim we tried to open a gym.
Actually I'm curious why this check is even here. This is the "are we at a place where there's a stop in the gmo" - not "we have tried to click a stop" ... anyhow. if gmo finds a gym here, it will fail spinnable check and reset spinnable
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But this is after the coords check and max accepted diff there is 0.00003. That gym would have been almost on top of pokestop, like ~4 meters MAX apart. Not saying not possible, but that must be a very very very special location :-)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I haven't followed this. But in my locality we have two gyms where people have moved pokestops right on top. Literally they show as underneath. So these situations do exist. These stops fail quest scan, but if you msg me on discord I will send you long,lat so you can see
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That log line is misleading. We're not yet trying to open anything there. I want to reset the counter every time we get a "defined" result. So finding a gym where we expected a stop is a defined result. The stop being disabled/closed/on cooldown is a defined result.
On the other hand - not finding the stop at all or having "no map data" is not a defined result, because it could possibly be some type of hiccup.