Builtin keyword produces KeywordNotFound error in VSCode

[Fightlapa]

Hi,

I'm trying to configure project after migrating from no longer supported VSCode plugin.

In general, I have quite good experience, I can navigate through files I have in my workspace. But when using builtin keywords, or just in general, those not created by me, VSCode has issues.

Any hints what I can have wrong here?
I am able to start test cases from IDE, and those work properly.

[d-biehl]

do you have any library imported with the name builtin or something like that? this could be override the builtin library.

Try to execute the vscode command RobotCode: Clear Cache and Restart Language Servers via F1

[Fightlapa]

Searched for any "builtin" import in my code and there is none. Not sure what dependencies are doing.

RobotCode: Clear Cache and Restart Language Servers
Didn't fix it - I noticed it restarted - all highlights from editor disappeared for a moment, but then once again all errors appeared again.

[d-biehl]

which version of Robot Framework and Python do you have?
Where is your python installed, System interpreter or venv? Are there any dependency problems?

[Fightlapa]

python3 -m pip freeze | grep robot
robotcode==2.1.0
robotcode-core==2.1.0
robotcode-modifiers==2.1.0
robotcode-plugin==2.1.0
robotcode-robot==2.1.0
robotcode-runner==2.1.0
robotframework==7.3
robotframework-mqttlibrary==0.7.1.post3
robotframework-requests==0.9.7
robotframework-retryfailed==0.2.0
robotframework-sshlibrary==3.8.0

I use venv

python3 --version
Python 3.10.12

Vscode version 1.106.3

[Fightlapa]

It seems it's some configuration clash. I have my project inside devcontainer, I created simplest example from youtube video you were presenting, so requirements.txt having:

robotframework
robotframework-tidy
robotframework-browser

And robot.robot having:

*** Test Cases ***
Simple check
    Log  Hello
    ${connection_establish_timeout} =  Set Variable    20
    Should be Equal  20  ${connection_establish_timeout}

• .venv created

Inside devcontainer it fails to find those

Execution still uses proper python, executes test and it's passing.

However on host (outside of devcontainer), exactly the same project structure results in proper behavior and I'm able to navigate to "Should be equal" implementation from builtin library

The only thing that for now could explain to me what modifies behavior is:
python.defaultInterpreterPath
which is different on Remote level of VSCode settings, but that doesn't make sense to me, as workspace configuration should have higher priority.

Not sure what previous plugin was using as it was working fine there, probably it had it own config management for python

[Fightlapa]

I found the difference.
I noticed that devcontainer has section:

     "mounts": [
      "source=/dev,target=/dev,type=bind,consistency=cached"
      ]

After I remove that, it works properly.
Then I started mapping manually each device. I cannot catch any device which starts to cause such problem. I mapped like 98% of those, where mapping last 2% directly is causing devcontainer to not build at all.

Is it known what could be the usage of /dev in that plugin?