{"action":"created","issue":{"url":"https://api.github.com/repos/Irbyz/aftershock-xe/issues/8","repository_url":"https://api.github.com/repos/Irbyz/aftershock-xe","labels_url":"https://api.github.com/repos/Irbyz/aftershock-xe/issues/8/labels{/name}","comments_url":"https://api.github.com/repos/Irbyz/aftershock-xe/issues/8/comments","events_url":"https://api.github.com/repos/Irbyz/aftershock-xe/issues/8/events","html_url":"https://github.com/Irbyz/aftershock-xe/issues/8","id":341110255,"node_id":"MDU6SXNzdWUzNDExMTAyNTU=","number":8,"title":"/timeout is bugged","user":{"login":"oamrjj","id":34872285,"node_id":"MDQ6VXNlcjM0ODcyMjg1","avatar_url":"https://avatars2.githubusercontent.com/u/34872285?v=4","gravatar_id":"","url":"https://api.github.com/users/oamrjj","html_url":"https://github.com/oamrjj","followers_url":"https://api.github.com/users/oamrjj/followers","following_url":"https://api.github.com/users/oamrjj/following{/other_user}","gists_url":"https://api.github.com/users/oamrjj/gists{/gist_id}","starred_url":"https://api.github.com/users/oamrjj/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/oamrjj/subscriptions","organizations_url":"https://api.github.com/users/oamrjj/orgs","repos_url":"https://api.github.com/users/oamrjj/repos","events_url":"https://api.github.com/users/oamrjj/events{/privacy}","received_events_url":"https://api.github.com/users/oamrjj/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-07-13T18:05:31Z","updated_at":"2018-07-15T21:34:48Z","closed_at":"2018-07-15T21:34:48Z","author_association":"NONE","body":"Hello,\r\nThere are multiple problems with timeout. I just tried it again (vs bots to test - set g_timeoutallowed 100). When one is in the water when a /timeout is done he will die at the end of the timeout.\r\nWhen doing /timeout the clock stops which is nice. after some testing when doing timeout the clock jumps forward but after the timeout it's again at the before timeout value."},"comment":{"url":"https://api.github.com/repos/Irbyz/aftershock-xe/issues/comments/405120119","html_url":"https://github.com/Irbyz/aftershock-xe/issues/8#issuecomment-405120119","issue_url":"https://api.github.com/repos/Irbyz/aftershock-xe/issues/8","id":405120119,"node_id":"MDEyOklzc3VlQ29tbWVudDQwNTEyMDExOQ==","user":{"login":"borg42","id":586478,"node_id":"MDQ6VXNlcjU4NjQ3OA==","avatar_url":"https://avatars2.githubusercontent.com/u/586478?v=4","gravatar_id":"","url":"https://api.github.com/users/borg42","html_url":"https://github.com/borg42","followers_url":"https://api.github.com/users/borg42/followers","following_url":"https://api.github.com/users/borg42/following{/other_user}","gists_url":"https://api.github.com/users/borg42/gists{/gist_id}","starred_url":"https://api.github.com/users/borg42/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/borg42/subscriptions","organizations_url":"https://api.github.com/users/borg42/orgs","repos_url":"https://api.github.com/users/borg42/repos","events_url":"https://api.github.com/users/borg42/events{/privacy}","received_events_url":"https://api.github.com/users/borg42/received_events","type":"User","site_admin":false},"created_at":"2018-07-15T21:34:48Z","updated_at":"2018-07-15T21:34:48Z","author_association":"COLLABORATOR","body":"This is a tricky one. During a timeout the internal clock doesn't stop running, so every timer that runs has to be incremented by the timeout time.\r\n\r\nI tried to stop the internal clock, but this always results in the \"Connection Interrupted\" state. So some part of the underlying engine probably thinks that the client got out of sync and drops it.\r\n\r\nI added the timeout time to all of the relevant timers i could find, but there are many 100 timers running and it is not easily obvious which one has to be increased and which one can't be increased.\r\n\r\nSo if you find another timeout bug please reopen the issue."}}
{"actor":{"display_login":"borg42"}}