{"push_id":1078338233,"size":1,"distinct_size":1,"ref":"refs/heads/catch-ELOOP","head":"40d269fdb41f77488ac4588fe1a3208c5bb81265","before":"d12917bd66f1a3f3349b6e24bc14a1a1939bce8f","commits":[{"sha":"40d269fdb41f77488ac4588fe1a3208c5bb81265","author":{"email":"b0c9a348ea900a493402ad782bca66f04feea3f9@us.ibm.com","name":"Myles Borins"},"message":"fix: catch ELOOP\n\nfs.realpath has been optimized to utilize `ev_fs_realpath()`, a new api\nin libuv. The libuv api has slightly different behavior. There are two\nparticular issues that are causing problems for glob\n\n* `ev_fs_realpath()` throwing before `fs.readdir` ELOOP\n* The removal of the cache\n\nIn the past glob was relying on `fs.readdir` to throw when handling\nrecursive symbolically linked directories. It is now possible that the\ncall to libuv can throw before. The behavior is currently different on\nosx and linux causing the test suite to fail on all of the flavors of\nlinux we are running in CI.\n\nThis commit adds an extra check for 'ELOOP' and sets appropriately.\n\nThere is an a check included to make sure that real\n\nref: https://github.com/libuv/libuv/pull/531\nref: https://github.com/nodejs/node/pull/3594","distinct":true,"url":"https://api.github.com/repos/TheAlphaNerd/node-glob/commits/40d269fdb41f77488ac4588fe1a3208c5bb81265"}]}