{"action":"opened","issue":{"url":"https://api.github.com/repos/commercialhaskell/stack/issues/1979","repository_url":"https://api.github.com/repos/commercialhaskell/stack","labels_url":"https://api.github.com/repos/commercialhaskell/stack/issues/1979/labels{/name}","comments_url":"https://api.github.com/repos/commercialhaskell/stack/issues/1979/comments","events_url":"https://api.github.com/repos/commercialhaskell/stack/issues/1979/events","html_url":"https://github.com/commercialhaskell/stack/issues/1979","id":144914301,"number":1979,"title":"runInteractiveProcess: pipe: resource exhausted error.","user":{"login":"wpoosanguansit","id":90733,"avatar_url":"https://avatars.githubusercontent.com/u/90733?v=3","gravatar_id":"","url":"https://api.github.com/users/wpoosanguansit","html_url":"https://github.com/wpoosanguansit","followers_url":"https://api.github.com/users/wpoosanguansit/followers","following_url":"https://api.github.com/users/wpoosanguansit/following{/other_user}","gists_url":"https://api.github.com/users/wpoosanguansit/gists{/gist_id}","starred_url":"https://api.github.com/users/wpoosanguansit/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/wpoosanguansit/subscriptions","organizations_url":"https://api.github.com/users/wpoosanguansit/orgs","repos_url":"https://api.github.com/users/wpoosanguansit/repos","events_url":"https://api.github.com/users/wpoosanguansit/events{/privacy}","received_events_url":"https://api.github.com/users/wpoosanguansit/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-03-31T14:15:35Z","updated_at":"2016-03-31T14:15:35Z","closed_at":null,"body":"I am using Stack on Mac El Capitan with resolver lt-5.10.  I ran into \r\n\r\nstack build --file-watch\r\n\r\nand it ran a few times before giving this errors:\r\n\r\n\r\nuser error (could not create file system event stream)\r\n\r\nand\r\n\r\n/usr/local/bin/ghc-pkg: streamingProcess: runInteractiveProcess: pipe: resource exhausted (Too many open files)\r\n\r\nafter running a few successful sessions.  I am not totally sure if the default limit set was too low or the file-watch just does not clean up things as it should.  In any case, I decided to fix it by increasing the ulimit by following the steps in this blog:\r\n\r\nhttp://blog.dekstroza.io/ulimit-shenanigans-on-osx-el-capitan/\r\n\r\nIt gets back to a working state again.  But again, not totally sure if this is the right solution.  Thanks for  your help.  "}}