{"action":"created","issue":{"url":"https://api.github.com/repos/SickRage/SickRage/issues/1259","repository_url":"https://api.github.com/repos/SickRage/SickRage","labels_url":"https://api.github.com/repos/SickRage/SickRage/issues/1259/labels{/name}","comments_url":"https://api.github.com/repos/SickRage/SickRage/issues/1259/comments","events_url":"https://api.github.com/repos/SickRage/SickRage/issues/1259/events","html_url":"https://github.com/SickRage/SickRage/issues/1259","id":143731638,"number":1259,"title":"Statvfs incorrect results on OSX","user":{"login":"bobbysteel","id":295361,"avatar_url":"https://avatars.githubusercontent.com/u/295361?v=3","gravatar_id":"","url":"https://api.github.com/users/bobbysteel","html_url":"https://github.com/bobbysteel","followers_url":"https://api.github.com/users/bobbysteel/followers","following_url":"https://api.github.com/users/bobbysteel/following{/other_user}","gists_url":"https://api.github.com/users/bobbysteel/gists{/gist_id}","starred_url":"https://api.github.com/users/bobbysteel/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bobbysteel/subscriptions","organizations_url":"https://api.github.com/users/bobbysteel/orgs","repos_url":"https://api.github.com/users/bobbysteel/repos","events_url":"https://api.github.com/users/bobbysteel/events{/privacy}","received_events_url":"https://api.github.com/users/bobbysteel/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-03-26T17:14:39Z","updated_at":"2016-03-26T17:14:40Z","closed_at":null,"body":"This is more of an OS level problem, but I wanted to get some feedback on it.\r\n\r\nCurrently using OSX and with network shares there are inconsistent results. I've got a Synology mounted on NFS and Samba both and statvfs returns wildly incorrect results when mounted. The _df _command works correctly and consistently however. I'd be interested in writing a patch to include an if statement for OSX where it uses the subprocess library to call /bin/df and then parse that result for disk space. Would anyone object to this?\r\n"},"comment":{"url":"https://api.github.com/repos/SickRage/SickRage/issues/comments/201894850","html_url":"https://github.com/SickRage/SickRage/issues/1259#issuecomment-201894850","issue_url":"https://api.github.com/repos/SickRage/SickRage/issues/1259","id":201894850,"user":{"login":"SickRage2","id":15840237,"avatar_url":"https://avatars.githubusercontent.com/u/15840237?v=3","gravatar_id":"","url":"https://api.github.com/users/SickRage2","html_url":"https://github.com/SickRage2","followers_url":"https://api.github.com/users/SickRage2/followers","following_url":"https://api.github.com/users/SickRage2/following{/other_user}","gists_url":"https://api.github.com/users/SickRage2/gists{/gist_id}","starred_url":"https://api.github.com/users/SickRage2/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/SickRage2/subscriptions","organizations_url":"https://api.github.com/users/SickRage2/orgs","repos_url":"https://api.github.com/users/SickRage2/repos","events_url":"https://api.github.com/users/SickRage2/events{/privacy}","received_events_url":"https://api.github.com/users/SickRage2/received_events","type":"User","site_admin":false},"created_at":"2016-03-26T17:14:40Z","updated_at":"2016-03-26T17:14:40Z","body":"Thanks for the issue report! Before a real human comes by, please make sure your report has all the below criteria checked\n\n- [ ] Include basic information: Branch/Commit, OS, What you did, What happened, What you expected\n- [ ] Enable debug logging (be sure to disable after the bug is fixed)\n- [ ] Post debug logs, either inline (for smaller logs) or using gist\n\nPlease make sure you also read [how to create an issue](https://github.com/SickRage/sickrage-issues/blob/master/README.md) and followed all of the steps. \n\nThe title should describe your issue. Having \"SR not working\" or \"I get this bug\" for 100 issues, isn't really helpful. We will close issues if there isn't enough information.\n\nSometimes the devs may seem like grunts and respond with short answers. This isn't (always) because the dev hates you, but because he's on mobile or busy fixing bugs. If something isn't clear, please let us know, and this bot may get updated to automatically answer you.\n\nThanks!"}}