Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Unable to resolve interpreter" when trying to run the base Action template on mac #43

Open
kariharju opened this issue Jun 14, 2024 · 3 comments
Labels
Bug Something isn't working

Comments

@kariharju
Copy link
Contributor

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.

  1. Create new action from template action-server create
  2. Try to run the default action from VS Code sidebar

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:

  • OS: MacOS
  • VSCode 1.88,
  • Microsoft Python extension v2024.4.1 all green
  • Robocorp Code: 1.19.0

We have issue extension logs under id #4373

@kariharju kariharju added Bug Something isn't working robocorp-code labels Jun 14, 2024
@kariharju
Copy link
Contributor Author

Comment by kariharju
Thursday Apr 11, 2024 at 15:00 GMT


Tried reproducing on another macOS Ventura 13.2.1, with the versions above, cannot repro

@kariharju
Copy link
Contributor Author

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.

@kariharju
Copy link
Contributor Author

Comment by zjffdu
Monday Apr 29, 2024 at 08:26 GMT


I have the same issue, have you solved this issue? @kariharju

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant