{"action":"created","issue":{"url":"https://api.github.com/repos/PokemonGoF/PokemonGo-Bot/issues/2262","repository_url":"https://api.github.com/repos/PokemonGoF/PokemonGo-Bot","labels_url":"https://api.github.com/repos/PokemonGoF/PokemonGo-Bot/issues/2262/labels{/name}","comments_url":"https://api.github.com/repos/PokemonGoF/PokemonGo-Bot/issues/2262/comments","events_url":"https://api.github.com/repos/PokemonGoF/PokemonGo-Bot/issues/2262/events","html_url":"https://github.com/PokemonGoF/PokemonGo-Bot/issues/2262","id":168718482,"number":2262,"title":"[Bug] FollowCluster can't decide where to go","user":{"login":"mattias","id":63664,"avatar_url":"https://avatars.githubusercontent.com/u/63664?v=3","gravatar_id":"","url":"https://api.github.com/users/mattias","html_url":"https://github.com/mattias","followers_url":"https://api.github.com/users/mattias/followers","following_url":"https://api.github.com/users/mattias/following{/other_user}","gists_url":"https://api.github.com/users/mattias/gists{/gist_id}","starred_url":"https://api.github.com/users/mattias/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mattias/subscriptions","organizations_url":"https://api.github.com/users/mattias/orgs","repos_url":"https://api.github.com/users/mattias/repos","events_url":"https://api.github.com/users/mattias/events{/privacy}","received_events_url":"https://api.github.com/users/mattias/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":13,"created_at":"2016-08-01T19:07:23Z","updated_at":"2016-08-02T15:47:36Z","closed_at":null,"body":"### Expected Behavior\r\nKeep moving towards the cluster and stay there.\r\n\r\n### Actual Behavior\r\nIt keeps going back and forth everywhere without ever reaching a destination.\r\nSnippet from the log:\r\n[21:02:57] Move to destiny. 2 lured pokestops will be in range of 50m. Arrive in 198.367797336m.\r\n[21:03:01] Move to destiny. 3 lured pokestops will be in range of 50m. Arrive in 768.134850221m.\r\n[21:03:05] Move to destiny. 2 lured pokestops will be in range of 50m. Arrive in 201.382109383m.\r\n[21:03:08] Move to destiny. 3 lured pokestops will be in range of 50m. Arrive in 767.946828573m.\r\n[21:03:13] Move to destiny. 3 lured pokestops will be in range of 50m. Arrive in 755.177316489m.\r\n[21:03:17] Move to destiny. 2 lured pokestops will be in range of 50m. Arrive in 209.438889512m.\r\n[21:03:21] Move to destiny. 3 lured pokestops will be in range of 50m. Arrive in 755.439571063m.\r\n[21:03:25] Move to destiny. 2 lured pokestops will be in range of 50m. Arrive in 208.935773283m.\r\n[21:03:29] Move to destiny. 3 lured pokestops will be in range of 50m. Arrive in 754.81225207m.\r\n\r\n### Steps to Reproduce\r\nRun the FollowCluster task as specified in the example config.\r\nMy configuration:\r\nhttps://gist.github.com/mattias/3028bd2d2bd222a52400f5fe2a881fc3\r\n\r\nEdit:\r\nAfter a while it finally settled down on one spot. \r\nI assume this happens when there are a lot of clusters with a lot of lured pokestops around.\r\nI'd still say it is a bug and has to have better priorities and stay focused on one target.\r\nIn the example above there were one cluster with 2 lured pokestops which was only 200m away and one cluster with 3 lured pokestops but 750m away. I've also had this happen when there has been two clusters with 2 lured pokestops each.\r\n\r\n### Other Information\r\nOS: Linux\r\nGit Commit: 494bc055543c3cb674cca781ec545311d3c9bad1\r\nPython Version: Python 2.7.12\r\n"},"comment":{"url":"https://api.github.com/repos/PokemonGoF/PokemonGo-Bot/issues/comments/236947426","html_url":"https://github.com/PokemonGoF/PokemonGo-Bot/issues/2262#issuecomment-236947426","issue_url":"https://api.github.com/repos/PokemonGoF/PokemonGo-Bot/issues/2262","id":236947426,"user":{"login":"th3w4y","id":10997651,"avatar_url":"https://avatars.githubusercontent.com/u/10997651?v=3","gravatar_id":"","url":"https://api.github.com/users/th3w4y","html_url":"https://github.com/th3w4y","followers_url":"https://api.github.com/users/th3w4y/followers","following_url":"https://api.github.com/users/th3w4y/following{/other_user}","gists_url":"https://api.github.com/users/th3w4y/gists{/gist_id}","starred_url":"https://api.github.com/users/th3w4y/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/th3w4y/subscriptions","organizations_url":"https://api.github.com/users/th3w4y/orgs","repos_url":"https://api.github.com/users/th3w4y/repos","events_url":"https://api.github.com/users/th3w4y/events{/privacy}","received_events_url":"https://api.github.com/users/th3w4y/received_events","type":"User","site_admin":false},"created_at":"2016-08-02T15:47:36Z","updated_at":"2016-08-02T15:47:36Z","body":"@MFizz yes.. i am also puzzled cause i also run the same function on every collected point and got the same point as destination each time\r\n\r\nand yes i am sure the logs are fine because i generated the cluster.log like this:\r\n\r\n```\r\nwith open('cluster.log', 'wb') as f:\r\n    while True:\r\n        f.write(str(bot.get_forts())+'\\n')\r\n        bot.tick()\r\n   ....:  \r\n```\r\n\r\nand then pasted the output and generated the log...\r\n>MFizz commented 5 hours ago • edited\r\n>Sorry I put every fort list you posted into find_biggest_cluster and got consistent output, >additionally I find 5 instead of 2 spots in your data. Maybe, you attached the wrong logs or you got >weird output from stepwalker?"}}
{"actor":{"display_login":"th3w4y"}}