You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As I am willing to update/fork rm-modules for the possible Out of memory I am facing too (hughsk/rm-modules#5), updating readdirp with version 3.5 and its "infinite loop" fix seems perfect,
3.5 (Oct 13, 2020) disallows recursive directory-based symlinks. Before, it could have entered infinite loop.
but Should it be possible to not destroy and exit on error in this case? like adding recursive to NORMAL_FLOW_ERRORS
In rm-modules case, the expected behavior would be to continue and process all but the problematic entry.
The text was updated successfully, but these errors were encountered:
As I am willing to update/fork rm-modules for the possible Out of memory I am facing too (hughsk/rm-modules#5), updating readdirp with version 3.5 and its "infinite loop" fix seems perfect,
but Should it be possible to not destroy and exit on error in this case? like adding recursive to NORMAL_FLOW_ERRORS
In rm-modules case, the expected behavior would be to continue and process all but the problematic entry.
The text was updated successfully, but these errors were encountered: