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

Unhelpful errors on non existing target in configuration file on IntelliJ #1392

Closed
t4lz opened this issue May 8, 2023 · 0 comments · Fixed by #1409
Closed

Unhelpful errors on non existing target in configuration file on IntelliJ #1392

t4lz opened this issue May 8, 2023 · 0 comments · Fixed by #1409
Assignees
Labels
bug Something isn't working intellij-extension ux

Comments

@t4lz
Copy link
Member

t4lz commented May 8, 2023

Bug Description

When running with mirrord on PyCharm (probably also on other IntelliJ based IDEs), with a target that does not exist in the configuration, the run fails with many errors that don't say what the problem is:
image

and running is then disabled:
image

We should tell the user why running failed, and no let the error escalate all the way to an IDE error.

Steps to Reproduce

  1. Open the python-e2e dir in PyCharm.
  2. Click on mirrord's configuration button.
  3. Add
        "target": {
            "path": "deploy/some-non-existing-name"
        }
    to the config file.
  4. Enable mirrord.
  5. Run.

Backtrace

No response

Relevant Logs

No response

Your operating system and version

macOS 13.3

Local process

python3

Local process version

No response

Additional Info

No response

@t4lz t4lz added bug Something isn't working ux intellij-extension labels May 8, 2023
@t4lz t4lz changed the title Unhelpful errors on bad target in configuration file on IntelliJ Unhelpful errors on non existing target in configuration file on IntelliJ May 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working intellij-extension ux
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants