`*,cover` in `excludeFile` breaks downward sync in `devspace sync` about devspace

[lizardruss]

Ah, thank you. Helps if I read the whole thread. This will take some additional debugging, since these patterns are matched by a 3rd party library, and its not clear if this issue lies there or in DevSpace. We'll update when we know more 👍

[lizardruss]

@MaxSchambach

I was trying to figure out what that pattern is supposed to match.. but it appears it may have been a typo that made its way into the wild. That assumption is according to this PR, but if there's an explanation of what that pattern means, we can look into it more.

[MaxSchambach]

The pattern is meant in a literal way, in particular matching <filename.py>,cover (as included also in the default GitHub repo which was brought back in this commit).

I agree, it looks very unusual, but is, unfortunately, the naming convention that coverage.py uses to report per-file coverage, see also this StackExchange thread. It mentions the PR you also linked, but the discussion of that PR also mentions that this is indeed not a typo, see here.

[MaxSchambach]

Any update on this?