Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

FileCollector not respecting directories options

See original GitHub issue

Describe the bug When specifying multiple directories for the file system collector, Only the first directory has results. This only occurs on Windows 8, Windows Server 2012, Windows Server 2012R2. Does not occur on Windows 10, Windows Server 2016, Windows Server 2019.

To Reproduce Steps to reproduce the behavior:

Run asa.exe -f --verbose --directories "C:\Program Files","C:\Windows\System32" Note: you can use different directories and also add more if you want
Observe that the file system collector parses the first directory and does not go to the next specified directory.
File Collector completes

Expected behavior To parse all directories given.

Screenshots Capture_File1 Capture_File2

System Configuration:

OS: Windows
OS Version: Windows 8, Windows Server 2012, Windows Server 2012R2
Application Version: v2.2.41+4cdefe4f55
CLI or GUI: CLI

Additional Context

Issue Analytics

State:
Created 3 years ago
Reactions:1
Comments:9 (7 by maintainers)

Top GitHub Comments

1reaction

gfscommented, Jun 3, 2020

It’s very strange. Powershell should work so thanks for your report. I think it’s fine to go with caret delimiters and just sidestep this while windows 8 weirdness

-------- Original Message -------- On Jun 3, 2020, 12:09 PM, a-gazin wrote:

Actually this may have been due to user error and I apologize. I have been using powershell to run ASA. From what i have observed, comparing powershell to command prompt (before your changes v2.2.41).

Powershell: Asa.exe collect -f --directories “C:\Program Files (x86)”,“C:\Program Files”: only the first works Asa.exe collect -f --directories “C:\Program Files (x86),C:\Program Files”: both work

Command Prompt: Asa.exe collect -f --directories “C:\Program Files (x86)”,“C:\Program Files”: both work Asa.exe collect -f --directories “C:\Program Files (x86),C:\Program Files”: both work

From my understanding the “,” character in the command line has significant value in powershell. It is strange how this is only present in Win8, WinS2012, WinS2012R2.

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or unsubscribe.

1reaction

gfscommented, Jun 2, 2020

I opened an issue with the maintainer of the library we use as well.

https://github.com/commandlineparser/commandline/issues/640