From 83d10c5a4a207b79a7faaf0fad37a54f3220f8f0 Mon Sep 17 00:00:00 2001 From: Jan Bouwhuis Date: Mon, 25 Mar 2024 11:26:03 +0100 Subject: [PATCH] Cleanup note about pythonTestAdapter work-a-round (#2122) --- docs/development_environment.mdx | 22 ---------------------- 1 file changed, 22 deletions(-) diff --git a/docs/development_environment.mdx b/docs/development_environment.mdx index 0bfb7822..432c7c3d 100644 --- a/docs/development_environment.mdx +++ b/docs/development_environment.mdx @@ -57,28 +57,6 @@ When a task is currently running (like `Preview` for the docs), it can be restar If the Dev Container was set up correctly - it supports debugging by default, out-of-the-box. It provides the necessary debug configurations, so hitting F5 should launch Home Assistant. Any breakpoints put in the code should be triggered, and the debugger should stop. -:::note -If debugging of tests fails with the built-in `pytest` adapter with: - -```text -vscode_pytest.VSCodePytestError: Error attempting to connect to extension communication socket[vscode-pytest]: A test tried to use socket.socket. -``` - -- Open `vscode` with Visual Studio Code and open the Home Assistant Dev Container. -- Open the command palette with: `Ctrl` + `Shift` + `P` -- Type `settings` command then select `>Preferences: Open Remote Settings (JSON) (Dev Container: Home Assistant Dev)`. -- Add `"python.experiments.optOutFrom": ["pythonTestAdapter"]` to the `settings.json` file. -- Restart the Dev Container to ensure the changes are effective. - -```json -{ - ..., - "python.experiments.optOutFrom": ["pythonTestAdapter"] -} -``` - -::: - It is also possible to debug a remote Home Assistance instance (e.g., production instance) by following the procedure described [here](https://www.home-assistant.io/integrations/debugpy/). ## Manual Environment