Problems with NCS on VScode

RE: Problems with NCS on VScode

Elfving — Mon, 10 Oct 2022 11:30:21 GMT

Heheh wow didn't see that coming, but that's great! I was about to ask him about this myself.

Then I'll consider this practically solved already.

Regards,

Elfving

RE: Problems with NCS on VScode

jonas.woerner — Mon, 10 Oct 2022 11:20:15 GMT

yes exactly.

I just got an answer from Trond Snekvik, and he told me he is aware of the issue and already started fixing it 🙂

RE: Problems with NCS on VScode

Elfving — Mon, 10 Oct 2022 11:17:14 GMT

[quote user="jonas.woerner"]do you know whats different about that nrf terminal in comparison to the normal terminal?[/quote]

I believe some path variables might be set, but not completely sure. I'll look into that.

So the issues now only show up when either building a project using west build, using the build action in the extension, or when running "bash" in the nrf terminal?

Regards,

Elfving

RE: Problems with NCS on VScode

jonas.woerner — Wed, 05 Oct 2022 10:26:33 GMT

I just tried it but its the same. nothing changed.

do you know whats different about that nrf terminal in comparison to the normal terminal? It doesnt seem to be the environment. If I could get this replicated in a system terminal it would help I guess..

EDIT: I found something I think.

I think it has something todo with this environment variable: BASH_FUNC_module%%=() { eval $($LMOD_CMD bash "$@") && eval $(${LMOD_SETTARG_CMD:-:} -s sh)

but I dont really know what its doing or how I can disable it. Im trying that now.

RE: Problems with NCS on VScode

Elfving — Wed, 05 Oct 2022 08:27:45 GMT

I see.

[quote user="jonas.woerner"]Im going to try the manual install.[/quote]

Great, I can imagine that making a difference. Let me know if it does.

Regards,

Elfving

RE: Problems with NCS on VScode

jonas.woerner — Wed, 05 Oct 2022 07:54:07 GMT

regarding the "entering bash". If I open an nRF terminal inside vscode and type sh or bash, I get these errors. I dont get them if I open a normal terminal in vscode.

I know its not an issue with the extensions perse, but an issue with the extensions on fedora. I just thought Nordic might be interested to fix this, as it doesnt seem like a big bug, but a small one that would enable fedora users a seemless experience.

my friend is using fedora too.

Im going to try the manual install.

RE: Problems with NCS on VScode

Elfving — Wed, 05 Oct 2022 06:49:32 GMT

Have you installed the nRF Command Line tools in addition to the SDK?

[quote user="jonas.woerner"]

should there be a manifest file on VScode projects? if so, where should it be as I cannot find it?

[/quote]

Well there is one in ncs/(ncs version)/nrf, are you finding that one?

[quote user="jonas.woerner"]

by building an NCS sample, I assumed you mean inside VScode. or did you mean using west CLI directly? I did this a while ago, and I dont remember the errors showing up there.

[/quote]

Any of the two, but yes please try it using the CLI directly too. As long as its a tested sample

[quote user="jonas.woerner"] I found out that entering "bash" into the nrf terminal also results in these errors.[/quote]

Could you expand on this? Are you saying that by opening the terminal and doing nothing you get these errors?

[quote user="jonas.woerner"]I think its an issue with the nordic extensions for VScode[/quote]

Well, if you only get these issues on Fedora I wouldn't say its an issue with the extension per se. nRF Connect officially only supports Windows, Mac and now the LTS version of Ubuntu, so there could be some issues related to it being Fedora. Did you do a manual installation, or did you install it using the Toolchain Manager? As you are not using any of the officially supported OS, I would recommend doing a manual install. And this does look like an installation issue.

I assume your friend uses Fedora too?

Regards,

Elfving

RE: Problems with NCS on VScode

jonas.woerner — Tue, 04 Oct 2022 21:15:01 GMT

ALso, I have to add, I just asked a friend of mine to just install the SDK and build a sample, and he can replicate my problem. the errors also show for him. so It has to be a bug in the nRF connect Extensions

RE: Problems with NCS on VScode

jonas.woerner — Tue, 04 Oct 2022 16:59:24 GMT

I tried some things, and I found out that entering "bash" into the nrf terminal also results in these errors. this does only happen if the terminal is opened as nrf connect terminal. opening a normal terminal (also in vscode) is not a problem.

RE: Problems with NCS on VScode

jonas.woerner — Tue, 04 Oct 2022 11:19:04 GMT

I am not able to run the west command from the nrf commandline. I get python errors here, but I fixed these. It still doesnt work though, as west cannot find a manifest file. when using the samples (in VScode, create new app and use a sample there) I get the same problems.

should there be a manifest file on VScode projects? if so, where should it be as I cannot find it?

by building an NCS sample, I assumed you mean inside VScode. or did you mean using west CLI directly? I did this a while ago, and I dont remember the errors showing up there.

I think its an issue with the nordic extensions for VScode.

RE: Problems with NCS on VScode

Elfving — Tue, 04 Oct 2022 11:14:00 GMT

I believe you can run the exact command that VSC does as long as you do it from the same folder - one with a manifest file.

[quote user="jonas.woerner"]

I am seeing these issues in the commandline output in VScode, but only when building an NCS app, nowhere else.

[/quote]

Are you able to run west commands from there? Could you try to build an NCS sample?

Regards,

Elfving

RE: Problems with NCS on VScode

jonas.woerner — Tue, 04 Oct 2022 09:33:40 GMT

I am seeing these issues in the commandline output in VScode, but only when building an NCS app, nowhere else.

you are right about the not valid build workspace. Is there a way to get the west manifest that VScode uses to build with west? or how could I try to reproduce the exact build procedure that vscode does from CLI? I cant run west from within the folder because the west manifest is missing from what I learned on your provided link.

RE: Problems with NCS on VScode

Elfving — Tue, 04 Oct 2022 06:30:54 GMT

[quote user="jonas.woerner"]I just installed everything (on Fedora) and it was like this.[/quote]

So if it is like this on Fedora, and you are not building from commandline, then where are you seeing these issues? In VSC? And are you seeing it eg. when opening a project, all the time, or just when building, or what?

[quote user="jonas.woerner"] I just tried to copy the build command to a terminal but that doesnt seem to work(west says "build" is not a valid option) but I will look into this and try it.[/quote]

Then I assume you are not launching it from a valid build workspace. See here for more details.

Regards,

Elfving

RE: Problems with NCS on VScode

jonas.woerner — Mon, 03 Oct 2022 11:07:57 GMT

Elfving I dont know how I got there, I just installed everything (on Fedora) and it was like this. Everything builds fine. building from commandline I have not tried. I just tried to copy the build command to a terminal but that doesnt seem to work(west says "build" is not a valid option) but I will look into this and try it.

RE: Problems with NCS on VScode

Elfving — Mon, 03 Oct 2022 11:01:42 GMT

Could you expand a bit on how you got that issue? Does it necessarily have anything to do with VSC, or are you getting it also by just building a project in a terminal? Is getting hundreds of those "/bin/sh:" lines the only thing you are getting? Are there any errors there as well?

Regards,

Elfving

RE: Problems with NCS on VScode

jonas.woerner — Mon, 03 Oct 2022 10:00:24 GMT

well, none of these addresses my Problem with the hundrets of error lines I mentioned. and that is the most annoying at the moment.

RE: Problems with NCS on VScode

Elfving — Mon, 03 Oct 2022 09:00:03 GMT

Hello Jonas,

That sounds rough. Like FanBoy mentioned you might have an easier time finding solutions by searching for the issues you run into individually.

When it comes to the issue you're having with Windows, is the lack of compiler errors in the Problems tab essentially the only issue? I believe this is a VSC problem, and not necessarily NCS related.

Regards,

Elfving

RE: Problems with NCS on VScode

nRF5xFanboy — Sat, 01 Oct 2022 05:29:18 GMT

Hello Jonas,

A few more people have that VSCode issue, just google for it

https://github.com/microsoft/vscode-arduino/issues/890

https://stackoverflow.com/questions/63372175/visual-studio-code-is-not-highlighting-compile-errors-in-my-code

https://www.reddit.com/r/vscode/comments/o9i9hv/vs_code_not_displaying_errors_in_problems_tab/

https://community.sonarsource.com/t/vscode-info-lint-not-showing-in-problems-tab/36602

nRF Extension on VScode doesn't doesn't bring compiler errors to PROBLEMS tab

Hope you find your answers & solutions there

Best regards,
nRF5XFanBoy