{"action":"created","issue":{"url":"https://api.github.com/repos/gilestrolab/ethoscope/issues/16","labels_url":"https://api.github.com/repos/gilestrolab/ethoscope/issues/16/labels{/name}","comments_url":"https://api.github.com/repos/gilestrolab/ethoscope/issues/16/comments","events_url":"https://api.github.com/repos/gilestrolab/ethoscope/issues/16/events","html_url":"https://github.com/gilestrolab/ethoscope/issues/16","id":104226195,"number":16,"title":"Leap second breaks system","user":{"login":"qgeissmann","id":1399684,"avatar_url":"https://avatars.githubusercontent.com/u/1399684?v=3","gravatar_id":"","url":"https://api.github.com/users/qgeissmann","html_url":"https://github.com/qgeissmann","followers_url":"https://api.github.com/users/qgeissmann/followers","following_url":"https://api.github.com/users/qgeissmann/following{/other_user}","gists_url":"https://api.github.com/users/qgeissmann/gists{/gist_id}","starred_url":"https://api.github.com/users/qgeissmann/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/qgeissmann/subscriptions","organizations_url":"https://api.github.com/users/qgeissmann/orgs","repos_url":"https://api.github.com/users/qgeissmann/repos","events_url":"https://api.github.com/users/qgeissmann/events{/privacy}","received_events_url":"https://api.github.com/users/qgeissmann/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/gilestrolab/ethoscope/labels/bug","name":"bug","color":"eb6420"},{"url":"https://api.github.com/repos/gilestrolab/ethoscope/labels/Critical","name":"Critical","color":"e11d21"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2015-09-01T09:34:58Z","updated_at":"2015-09-01T18:51:48Z","closed_at":null,"body":"Looking in journalctl, we can see that a *leap second has been inserted*.\r\nImmediately after, devices raise an exception:\r\n\r\n```python        \r\ndt = float(t - self.last_t)\r\nif dt < 0:\r\n    raise EthoscopeException(\"Negative time interval between two consecutive frames\")\r\n```\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/gilestrolab/ethoscope/issues/comments/136826268","html_url":"https://github.com/gilestrolab/ethoscope/issues/16#issuecomment-136826268","issue_url":"https://api.github.com/repos/gilestrolab/ethoscope/issues/16","id":136826268,"user":{"login":"PolygonalTree","id":5161395,"avatar_url":"https://avatars.githubusercontent.com/u/5161395?v=3","gravatar_id":"","url":"https://api.github.com/users/PolygonalTree","html_url":"https://github.com/PolygonalTree","followers_url":"https://api.github.com/users/PolygonalTree/followers","following_url":"https://api.github.com/users/PolygonalTree/following{/other_user}","gists_url":"https://api.github.com/users/PolygonalTree/gists{/gist_id}","starred_url":"https://api.github.com/users/PolygonalTree/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/PolygonalTree/subscriptions","organizations_url":"https://api.github.com/users/PolygonalTree/orgs","repos_url":"https://api.github.com/users/PolygonalTree/repos","events_url":"https://api.github.com/users/PolygonalTree/events{/privacy}","received_events_url":"https://api.github.com/users/PolygonalTree/received_events","type":"User","site_admin":false},"created_at":"2015-09-01T18:51:48Z","updated_at":"2015-09-01T18:51:48Z","body":"Negative times are due to the difference in microseconds.\nI don't get why the kernel should change the time in devices. It is provided and managed by NTP service. \n\n\n> El 01/09/2015, a las 11:24, Quentin Geissmann <notifications@github.com> escribió:\n> \n> I don't think it is a simple time drift issue as all devices that were tracking crashed at the exact same time.\n> This look more like a kernel 'bug' to be.\n> \n> —\n> Reply to this email directly or view it on GitHub.\n> \n"}}