{"issue":{"created_at":"2011-12-11T10:32:58Z","state":"open","updated_at":"2011-12-11T10:32:58Z","user":{"gravatar_id":"efba8ca1758acda2032c79b9ff4cd60b","id":878949,"url":"https://api.github.com/users/viloocity","avatar_url":"https://secure.gravatar.com/avatar/efba8ca1758acda2032c79b9ff4cd60b?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","login":"viloocity"},"comments":0,"body":"The issue has been discussed on stackoverflow.com ( http://stackoverflow.com/questions/8456981/runtime-error-with-0mq-haskell-binding-getintopt-interrupted-interrupted-syst ) and is probably best described there. \r\n\r\nIt would be definitively helpful to get at first a fix as described. However, I also observe this frequently with e.g. 16Kb long messages where it might in practice not be feasible to permanently have to restart the loop?","assignee":null,"id":2515450,"labels":[],"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"number":9,"title":"When large amounts of messages are sent/received or large amounts of data are transferred 0MQ fails with the error: getIntOpt: interrupted (Interrupted system call)","html_url":"https://github.com/twittner/zeromq-haskell/issues/9","closed_at":null,"url":"https://api.github.com/repos/twittner/zeromq-haskell/issues/9","milestone":null},"action":"opened"}