exception in config.py:status()

[Thomas-Henkel]

vs-code Version 1.78.2 installed on windows10 Version 20H2 installed ocp_vscode and build123d

exception KeyError ["text"] when running a build123d example using show_object(), config.py:status() called by config.py:combined_config() while use_status=False, after requests.get(f"{CMD_URL}:{port}/status") returns {}. only calling status() when use_status=True worked around the problem for me.

[bernhard-42]

I have problems in reproducing with the same versions of ocp_vscode and ocp_tessellate:

from build123d import *
from ocp_vscode import *

b = Box(1,2,3)

show_object(b)

works

Is the cad viewer extension also 1.0.0

[Thomas-Henkel]

Hi Bernhard,

yes, the viewer is v1.0.0 (see bottom of mail). The problem seems to be the answer {} from port 3939 when status is queried. The query config seems to work just fine. I tried it with the browser entering 127.0.0.1:3939/status and also saw {} as the only answer. When I tried to reproduce this today, the effect was gone. At the same time, when I saw this happen, I also always got a completely black widget for the OCP viewer. Today, I could not reproduce the issue, the widget came up with the ocp logo when started and the browser showed a status that contained a "text" key. I tried restarting the viewer and vscode multiple times but could no longer reproduce the problem.

I saw in a previous issue that the problem with the blank viewer at startup happened to others, as well, with the effect disappearing after a while. Very strange.

Now I just tried one last time restarting the viewer and there it is, again:

and here, what the browser says:

best regards,

Thomas

Am Fr., 2. Juni 2023 um 18:47 Uhr schrieb Bernhard @.***

:

I have problems in reproducing with the same versions of ocp_vscode and ocp_tessellate:

from build123d import from ocp_vscode import b = Box(1,2,3) show_object(b)

works

Is the cad viewer extension also 1.0.0 [image: image] https://user-images.githubusercontent.com/954408/242943950-20fccfcf-266d-41c0-a3c6-6fcf0ca13c6c.png

— Reply to this email directly, view it on GitHub https://github.com/bernhard-42/vscode-ocp-cad-viewer/issues/12#issuecomment-1574030887, or unsubscribe https://github.com/notifications/unsubscribe-auth/BAIKUYOTNOIZN3RN5ZAK55LXJIKINANCNFSM6AAAAAAYYCD6SM . You are receiving this because you authored the thread.Message ID: @.***>

[bernhard-42]

Thanks for the details, I will check when {} will be returned and where I need to add verifications that text is available. btw., unfortunately, the images are not visible here on github

[bernhard-42]

I still can't reproduce, but returning {} from the API call can only happen when

1. either the splash scene doesn't appear, or
2. when status() is called before the callback from showing the splash scene has been propagated.

I have changed status() to return {} when the API call returns {} This should help with 2.

Case 1. is a different problem that I still haven't understood. The CORS topic shouldn't be the reason any more, since the extension does not access the Internet for getting the three-cad-viewer component any more, but gets everything from the extension local node_modules folder.

I will further research it ...

[Thomas-Henkel]

Hi Bernhard,

In my case, returning {} clearly correlates with the missing splash scene. If I have the blank widget, I can check at any time later with the browser and still get {} for the status and the splash scene doesn't show up later, either. Your fix for dealing with the {} return value will work fine for me. The missing splash scene does not prevent me from showing an object from my code, later, given I'm not getting the exception, first.

Thanks for looking into this.

Best regards,

Thomas

Bernhard @.***> schrieb am So., 4. Juni 2023, 15:33:

I still can't reproduce, but returning {} from the API call can only happen when

1. either the splash scene doesn't appear, or
2. when status() is called before the callback from showing the splash scene has been propagated.

I have changed status() to return {} when the API call returns {} This should help with 2.

Case 1. is a different problem that I still haven't understood. The CORS topic shouldn't be the reason any more, since the extension does not access the Internet for getting the three-cad-viewer component any more, but gets everything from the extension local node_modules folder.

I will further research it ...

— Reply to this email directly, view it on GitHub https://github.com/bernhard-42/vscode-ocp-cad-viewer/issues/12#issuecomment-1575571832, or unsubscribe https://github.com/notifications/unsubscribe-auth/BAIKUYPXYJ3N6R4ZYZQJTY3XJSFDXANCNFSM6AAAAAAYYCD6SM . You are receiving this because you authored the thread.Message ID: @.***>

[bernhard-42]

If the missing splash screen happens again and you have some time, I would really appreciate if you could look into

• the Extension Host output

• The developer tools console

Do you see anything that looks like an OCP CAD Viewer problem?

[Thomas-Henkel]

here the extension host output for a vscode restart ending up with a blank ocp widget.

I then restarted ocp multiple times until I hit the blank widget, again. Nothing was added to the extension host output.

In the Developer Tools Console, I see

Multiple ocp restarts and one execution of box.py later, the Console looks like this

[bernhard-42]

Great, thank you. The line with glass is the issue. Now I know what to search for!

[bernhard-42]

Closing for now. If it still is an issue, please re-open