This looks like it could have to do with the new namespace linter. @UGNFXV1FA

@fabrao Does Calva print a clj-kondo version?

Can you also specify what you are using: Calva + clojure-lsp or the clj-kondo extension?

PS C:\> clj-kondo --version clj-kondo v2021.12.16

alright, thanks

can you try to make a repro with the updated clj-kondo on the command line too?

Is that also the version that Calva is using? Doesn’t it bundle its own instance of clj-kondo?

No, it's using the standalone clj-kondo plugin it seems, which is the newest version. clojure-lsp isn't using the newest clj-kondo yet.

@fabrao You could try disabling the :namespace-name-mismatch linter in your config, if that fixes it then it’s conclusive where the issue is. I’ll have a look at the source code but I didn’t think of paths including /c:/ so I’m not sure if that works.

Disabling that linter doesn't deactivate the code-path in which this error happens I think

Ok right

clj-kondo --version clj-kondo v2022.03.04 -> same result

@fabrao can you please specify an exact repro on the command line, including the filename

But if it’s going wrong with clj-kondo v2021.12.16 it must be something else…?

This is why I'm asking for an exact command line repro. Please test with the old and new version.

PS C:\Windows\System32> clojure -Sdeps '{:deps {clj-kondo/clj-kondo {:mvn/version \"2022.03.04\"}}}' -M -m clj-kondo.main --lint c:/Trabalho/Clientes/test/projeto/back-end/src/core.clj
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding='UTF-8'
linting took 106ms, errors: 0, warnings: 0

so strange !!!

so on the command line it behaves correctly?

clj-kondo --lint c:/Trabalho/Clientes/test/projeto/back-end/src/core.clj
linting took 9ms, errors: 0, warnings: 0

yes, no problem with command line

ok, please file an issue with the contents of the file and directory structure. Then I can try to reproduce using VSCode on Windows.

@UGNFXV1FA I guess you don't have access to a Windows machine right?

No. Maybe I could spin up a VM but it would take hours to get up and running. But the results above suggest it is unrelated to my PR, or am I misinterpreting?

Even when Calva Repl is not running, the problem happen

@fabrao can you downgrade the clj-kondo plugin to the previous version?

then we can be sure that it's not related to the new namespace linter...

clj-kondo does not use the Calva REPL

@fabrao this is how you do that:

Just to let you know, I tried with VSCODE + WSL 2 and no problem

@UGNFXV1FA I'll take a look on my Windows machine, no problem

yes, it's definitely Windows related and the only thing that comes to mind is that new namespace linter since that looks at the filename

Windows

even I installed with 2022.03.04 -> shows 2022.02.09

@fabrao to pin down the issue, can you please disable Calva and only use the clj-kondo extension. you have installed the clj-kondo plugin from which this error comes.

@U04V15CAJ you see, console is showing other version than installed

that console output comes from Calva, ignore it

and disable it

if you are using Calva you don't have to use the clj-kondo extension, since clojure-lsp already comes with clj-kondo included.

I disabled Calva, and the same problem happen

but now that you have bumped into this issue, let's take advantage of this and get to the bottom of it

yes, as I said, this is coming form the clj-kondo extension. please try the older version 2022.2.9 now

with older version, the problem gone

I re-enabled Clava, and it´s going ok

what a mess VSCODE did !

yes, so it's likely that it is introduced in the latest version. thanks for checking

you can uninstall the clj-kondo extension if you are using Calva

can you still make a Github issue for this?

It´s up to you

I have to use clj-kondo because I have clj-kondo in git action, so I have check it out before PR

yes, but if you are using Calva, you get clj-kondo as well, automatically

ok, I did´t know

> It´s up to you Well, please do

Thanks for discovering this problem before Calva/lsp updates clj-kondo though :)

If I didn´t use clj-kondo, I could not find the bug 🙂

I'll keep it to help community

thanks :)

https://github.com/clj-kondo/clj-kondo/issues/1605

Can you also specify the code in the file in the issue?

And also the full directory structure

so I can reproduce this locally

I think I've reproduced the problem:

user=> (fs/strip-ext ".c:.foo.bar")
java.nio.file.InvalidPathException: Illegal char <:> at index 2: .c:.foo.bar [at <repl>:7:1]

Pushing a fix to branch issue-1605-windows-test

fixed on master

will do a release tomorrow

Released and works in VSCode now

Ffffk, there is another problem on Windows

I'll disable this linter by default until these problems are solved