{"action":"closed","issue":{"url":"https://api.github.com/repos/pipobscure/fsevents/issues/42","labels_url":"https://api.github.com/repos/pipobscure/fsevents/issues/42/labels{/name}","comments_url":"https://api.github.com/repos/pipobscure/fsevents/issues/42/comments","events_url":"https://api.github.com/repos/pipobscure/fsevents/issues/42/events","html_url":"https://github.com/pipobscure/fsevents/issues/42","id":48023532,"number":42,"title":"Error handling for OS X system limits","user":{"login":"es128","id":1740641,"avatar_url":"https://avatars.githubusercontent.com/u/1740641?v=3","gravatar_id":"","url":"https://api.github.com/users/es128","html_url":"https://github.com/es128","followers_url":"https://api.github.com/users/es128/followers","following_url":"https://api.github.com/users/es128/following{/other_user}","gists_url":"https://api.github.com/users/es128/gists{/gist_id}","starred_url":"https://api.github.com/users/es128/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/es128/subscriptions","organizations_url":"https://api.github.com/users/es128/orgs","repos_url":"https://api.github.com/users/es128/repos","events_url":"https://api.github.com/users/es128/events{/privacy}","received_events_url":"https://api.github.com/users/es128/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2014-11-06T22:30:23Z","updated_at":"2015-01-15T18:20:45Z","closed_at":"2015-01-15T18:20:45Z","body":"If too many fsevents instances are spawned, the underlying system components start to print errors that can't be caught in node-land. \r\n\r\nNode.js dealt with the same thing for `fs.watch` at https://github.com/joyent/node/issues/5463. The solution is in libuv at https://github.com/joyent/libuv/pull/894, but has not been backported to node 0.10.x.\r\n\r\nThe limit is 400-something, and I haven't come across any way to change it. As @indutny said, it almost seems like a practical joke Apple is playing on us.\r\n\r\nI'm not sure that the fsevents module ought to be rearranged as substantially as was done there, but if it could at least catch these errors and expose them via regular node callbacks or events that would be a great start in being able to come up with more elegant solutions to this limitation."}}