You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Comment by kariharju Thursday Apr 11, 2024 at 15:43 GMT
Disabling RFW LSP extension fixed this issue.
Enabling that back brought back the error.
Assuming that this could have something to do with old robot.yaml.bak and conda.yaml.bak files in the action repo.. but looks more like the LSP environment detection problem.
Still cannot reproduce the case on other Windows or Mac machines.
Issue by kariharju
Thursday Apr 11, 2024 at 14:46 GMT
Originally opened as robocorp/robotframework-lsp#1061
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
So far happened only on macOS machines, video below.
action-server create
Getting "Unable to resolve interpreter for: ... package.yaml"
Expected behavior
The action should just run.
Screenshots
https://github.com/robocorp/robotframework-lsp/assets/56814402/60778611-6289-4340-97e9-0744795ba3ae
Versions:
We have issue extension logs under id #4373
The text was updated successfully, but these errors were encountered: