[??BUG??] Possibly searching too often, take a rest.

[davidspeijer]

Expected Behavior

Bot walking around without any warnings

Actual Behavior

Getting the warning: Possibly searching too often, take a rest.
Strange thing is that I thought that this warning should only happen when spinning forts and not while walking between forts. Can anybody confirm this?

Your FULL config.json (remove your username, password, gmapkey and any other private info)

http://pastebin.com/Ekmrdh65

Output when issue occurred

[2016-09-03 11:29:23] [ SpinFort] [spun_pokestop] Spun pokestop xxx. Experience awarded: 50. Items awarded: 4x Pokeball
[2016-09-03 11:29:26] [MoveToFort] [moving_to_fort] Moving towards pokestop yyy - 0.18km
[2016-09-03 11:29:28] [ SpinFort] [pokestop_searching_too_often] Possibly searching too often, take a rest.
[2016-09-03 11:29:30] [ SpinFort] [pokestop_searching_too_often] Possibly searching too often, take a rest.
[2016-09-03 11:29:31] [ SpinFort] [pokestop_searching_too_often] Possibly searching too often, take a rest.
[2016-09-03 11:29:32] [ SpinFort] [pokestop_searching_too_often] Possibly searching too often, take a rest.
[2016-09-03 11:29:32] [MoveToFort] [moving_to_fort] Moving towards pokestop yyy - 0.17km
[2016-09-03 11:29:34] [ SpinFort] [pokestop_searching_too_often] Possibly searching too often, take a rest.
[2016-09-03 11:29:35] [ SpinFort] [pokestop_searching_too_often] Possibly searching too often, take a rest.
[2016-09-03 11:29:36] [ SpinFort] [pokestop_searching_too_often] Possibly searching too often, take a rest.
[2016-09-03 11:29:38] [ SpinFort] [pokestop_searching_too_often] Possibly searching too often, take a rest.
[2016-09-03 11:29:43] [MoveToFort] [moving_to_fort] Moving towards pokestop yyy - 0.13km

Steps to Reproduce

Running the bot

Other Information

OS: CentOS

Branch: dev

Git Commit: 83c1546

Python Version: 2.7

Any other relevant files/configs (eg: path files)

[julienlavergne]

You can pass by some forts while walking between two forts.
I have the same issue as well, I think it is due to recent changes in the spin_fort task. There is something wrong with how we recognize forts that we already spinned.

[amal]

Same issue

[rawgni]

same issue

[julienlavergne]

@sohje, @solderzzc
I think there is an issue with that commit 5b3cfbb. We are not relying anymore on fort_timeout list to discard forts. But we are still adding them to fort_timeout in case the API tells us we cannot spin.

[ProZer0]

Same issue here, I guess the bot spins the fort when it approachs the fort and another time when it starts to move towards another fort

[solderzzc]

@anakin5 Thanks for the PR. I saw this issue as well.

[julienlavergne]

Fixed