{"action":"opened","issue":{"url":"https://api.github.com/repos/AHAAAAAAA/PokemonGo-Map/issues/2562","repository_url":"https://api.github.com/repos/AHAAAAAAA/PokemonGo-Map","labels_url":"https://api.github.com/repos/AHAAAAAAA/PokemonGo-Map/issues/2562/labels{/name}","comments_url":"https://api.github.com/repos/AHAAAAAAA/PokemonGo-Map/issues/2562/comments","events_url":"https://api.github.com/repos/AHAAAAAAA/PokemonGo-Map/issues/2562/events","html_url":"https://github.com/AHAAAAAAA/PokemonGo-Map/issues/2562","id":168278352,"number":2562,"title":"Suspend scan loop without clients","user":{"login":"d4fseeker","id":287879,"avatar_url":"https://avatars.githubusercontent.com/u/287879?v=3","gravatar_id":"","url":"https://api.github.com/users/d4fseeker","html_url":"https://github.com/d4fseeker","followers_url":"https://api.github.com/users/d4fseeker/followers","following_url":"https://api.github.com/users/d4fseeker/following{/other_user}","gists_url":"https://api.github.com/users/d4fseeker/gists{/gist_id}","starred_url":"https://api.github.com/users/d4fseeker/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/d4fseeker/subscriptions","organizations_url":"https://api.github.com/users/d4fseeker/orgs","repos_url":"https://api.github.com/users/d4fseeker/repos","events_url":"https://api.github.com/users/d4fseeker/events{/privacy}","received_events_url":"https://api.github.com/users/d4fseeker/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-07-29T08:46:11Z","updated_at":"2016-07-29T08:46:11Z","closed_at":null,"body":"The server should have the ability to suspend active scan loops when no clients are connected and resume scanning when a client connects again. This prevents often needless load on the gameservers and thus prevents eventual ratelimiting.\r\n\r\n## Expected Behavior\r\nWhen the \"inactivity\" flag is set, the server should stop scanning the area after a configured time. If a client connects again, it should restart the scan loop and reset the timeout counter. On each client API request, reset the counter.\r\n\r\n## Current Behavior\r\nThe server currently scans non-stop, causing a significant load and bandwith usage on the gameservers while the grabbed data is wasted for the majority of the time if no additional tools are running.\r\n\r\n## Possible Solution\r\nWhen the inactivity CLI flag is set, the server counts the seconds from the last API request. If that value reaches the inactivity timeout, it suspends the scan loop. If a new request is detected or the location is changed, reset the inactivity timer and start the loop again.\r\n\r\n## Context\r\nThere is a risk of the server operators considering the average load too high and starting to block grabber tools solely because the number of requests per day is too high.\r\n\r\n## Your Environment\r\n* Version used: master\r\n* Environment name and version: Python 2.7\r\n* Operating System and version: Centos 7\r\n"}}
{"actor":{"display_login":"d4fseeker"}}