Can not show the image during debugging the python code.

[zhfkt]

Hi,

I am debugging the remote python code through wsl, and the plugin can not show the image during debugging the python code.

The logs says:

[2021-01-22 11:53:54.619] [exthost] [error] [johnguo.simply-view-image-for-python-opencv-debugging] provider FAILED
[2021-01-22 11:53:54.627] [exthost] [error] Error: Unable to find thread to evaluate variable reference.
at t.RawDebugSession.handleErrorResponse (file:///C:/Users/SHData/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:3369:750)
at file:///C:/Users/SHData/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:3369:55

Pls review.

Thank you !

[john-guo]

Hello,

I have tested with wsl and it's no problem. Do you install the extension in wsl? The extension must be installed in wsl not local if you want to debug in wsl.

[zhfkt]

Hi @john-guo

I installed the extension in both local and wsl env

Could we have some way to collect extension logs for what happened in my local envs ? then I could provide extension logs to you for futher debugging ?

[john-guo]

How do you start the debug? Could you paste some Python Debug Console outputs? Could you create a tiny python to test this issue, such as:

import numpy as np
import cv2

img = cv2.imread("test.jpg")

pass

or you can add some logs in ViewImageService.ts:

		let res = await session.customRequest('threads', {});
--------> console.log(res); 
		let threads = res.threads;
		let mainThread = threads[0].id;
--------> console.log(`main:${mainThread}`);

But I don't know if this will be helpful.

[zhfkt]

Hi @john-guo

Thank you for your the suggestion. I just saw the log from the "Log (Remote Extension)" in the output window in the following screenshot

Unfortunately I didn't have much time to debug further because I was too busy in recent days. I used another plugin from Pycharm on https://plugins.jetbrains.com/plugin/14371-opencv-image-viewer as an alternative choice. You could close this issue if you would like to close it.

[john-guo]

Hi zhfkt

It seems this issue is caused by multi-threading. Because the vscode debug api cannot provide the current thread id in active debug session, I use the first thread id to evaluate the expression. I will modify the limition description in ReadMe.Thank you.

[john-guo]

Hi @zhfkt

After some experimentation I made a workaround in multithreaded debugging. Hope it works for you. Thank you.