ignored_paths false positives

[athompson-a2]

I noticed today that a customer's WP installation wasn't getting found. Verbose output found the following:

[0:00:39] Matched ignored path. Skipping recursion into '/home/username/wpblogs/'

This seems to be matching "logs/" in ignored_path. This might have broken with #67 . Previously the line would have been /logs/, but something in the way it's looking now it's not using the preceding directory separator when matching. "blogs" is a pretty common directory for WP sites. I could also see "js/" resulting in false positives with the current way this is matching.

[jormaster3k]

Ran into the same issue. We have -data/ in the top level directory that we scan, so anything there was being ignored.

Workarounds include reverting to version 2.0.0

wp package install wp-cli/find-command:2.0.0

Alternatively, use the --skip-ignored-paths flag, but that may come at the cost of performance

[swissspidy]

#67 was aiming to address a Windows compat issue, so to confirm, is this happening on Windows or Linux?