file paths that includes parentheses causes base directory to be wrong

[Oobert]

If a file paths for items listed in files configuration section contains parentheses, the base directory for those files is incorrectly inferred.

Example:
C:\path\to\my\files\something(other thing)\anotherDirectory*.js

Base directory is inferred as:
C:\path\to\my\files\

instead of:
C:\path\to\my\files\something(other thing)\anoterDirectory\

This causes karma to watch all files in the wrong directory and may cause high CPU useage. In my case it was 80% cpu usage because it was watching 1000s of files.

Windows 7
Karma: 0.10.2

The cause is the regex in function baseDirFromPattern in watch.js
https://github.com/karma-runner/karma/blob/master/lib/watcher.js#L11

If I knew regex better or what exactly this was doing, I would attempt to fix it.

[vojtajina]

I don't understand this issue.

Why should ...\x\something(other thing)*.js produce base directory ...\x\something(other thing)*\ ? That makes no sense to me. This pattern means that any file in C:\path\to\my\files\ that matches something(other thing)*.js is matched. Therefore the whole C:\path/to\my\files\ directory has to be scanned.

[Oobert]

doh! my \ before *.js disappeared. Edited issue to be more clear. Previously there was a \ before *.js but I added anotherDirectory to make the example more clear. I hope this helps!

[yngvark]

I have run into this or a similar problem. I have a very simple karma project generating very high CPU loads, but only when the project is located in a deep directory path, including space and parantheses.

Relevant Karma config:
files: [
'test/Spec.js', // Contains 1 test file
'src/.js' // Contains 1 js-file
],

Running with --log-level debug reveals that Karma is watching lots of files in other directories on my hard drive.

I am running the Karma projects in these two locations:

1. d:\Temp\karmatest-simple
2. d:\Dropbox\LenovoT410 (1)\a\b\c\d\karmatest-simple\

Number one works fine, number two gives huge CPU load. This suggests that something with the path causes the problem. My gut feeling is that the space rather than parantheses is the problem.

Please tell if more details are required.

edit: spelling

[vojtajina]

Ok, I see now. Yep, the parentheses is the problem. I didn't know that just parenthesis does not mean any special glob/fnmatch pattern, so we can actually get parentheses to work.

I'm working on it.