topic Re: API debugger doesn't work after Oct 2019 update in Fusion API and Scripts Forum

API debugger doesn't work after Oct 2019 update

lorraine5RWGT — Tue, 08 Oct 2019 23:26:17 GMT

Debugger doesn't work the way it did since the update at the end of September. Clicked 'Debug' from the 'Add-in's and Scripts' window, which opens VSCode, click on the Configuration thing that says 'Python: Attach', and I only get the error 'Failed to Attach'.

Re: API debugger doesn't work after Oct 2019 update

kdrector — Thu, 10 Oct 2019 03:12:03 GMT

Selecting "Debug" while starting an addin causes a second fusion 360 window to open.

The original window meanwhile continued to run in non-debug mode.

A VSCode window was opened and displayed the source file as one would expect. However, clicking "start debugging" first showed the debug dropdown menu but then showed a dialog proclaiming "Failed to attach (connect ECONNREFUSED 127.0.0.1:9000) - cancel and Open launch.json buttons

About VSCode shows:

Version: 1.39.0
Commit: 9df03c6d6ce97c6645c5846f6dfa2a6a7d276515
Date: 2019-10-09T06:57:43.593Z
Electron: 4.2.10
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Darwin x64 17.7.0

Re: API debugger doesn't work after Oct 2019 update

goyals — Thu, 10 Oct 2019 14:29:12 GMT

It is possible to install old version of PTVSD extension through UI. Please take a look at the attached image. Go back to version 2019.9.34911 and restart VSCode. Then try to follow the usual workflow of debugging. Let us know If you still see issue. Thanks.

Re: API debugger doesn't work after Oct 2019 update

goyals — Thu, 10 Oct 2019 15:03:05 GMT

Please take a look at the attached video to overcome extension update issue. Do not forget to restart Fusion. Thanks.

Re: API debugger doesn't work after Oct 2019 update

lorraine5RWGT — Thu, 10 Oct 2019 19:50:08 GMT

Thanks, will try that out.

Another temporary workaround I found to at least get output from Python is to redirect stdout to a file:

import sys
sys.stdout = open('D:\\Documents\\python_output.txt', 'w')

It doesn't print errors, though. For errors, you can add in a try... except... and print the traceback, so that it's outputted to stdout.

Re: API debugger doesn't work after Oct 2019 update

JuergenGe — Thu, 17 Oct 2019 08:29:42 GMT

The solutions do not work.

It has worked before the update (at some point).

I go to Add-Ins->Scripts and Add-Ins->myscript. Select Debug.

Then VSCode opens. Open the debug session. Press the play button left to the "Python: Attach".

And then i get this:

Seems to me, that Fusion 360 is blocking the request.

Tested on two independent Windows PCs.

Changing version of the Python plugin does not work.

Any ideas?

Re: API debugger doesn't work after Oct 2019 update

JeromeBriot — Thu, 17 Oct 2019 10:35:08 GMT

@JuergenGe wrote:

Changing version of the Python plugin does not work.

Hello,

Did you restart Fusion 360?

Re: API debugger doesn't work after Oct 2019 update

JuergenGe — Thu, 17 Oct 2019 11:10:02 GMT

Ok you got me there. 🙂

I should have read both solution completely.

Tried it again and restarted Fusion 360.

Now it works again.

Can anybody explain why the older version of the Python extension is working?

Re: API debugger doesn't work after Oct 2019 update

Anonymous — Thu, 17 Oct 2019 11:19:29 GMT

Hi! I downgraded the plugin to the recommended version and restarted Fusion 360, but it still doesn't work.

Any idea why? Anything I can try?

Thanks!

Etienne

Re: API debugger doesn't work after Oct 2019 update

goyals — Thu, 17 Oct 2019 11:52:15 GMT

New version of python extension is not stable and lot of issues are already reported there. Once the bugs are fixed, we will consume it. Thanks.

Re: API debugger doesn't work after Oct 2019 update

Rushikesh.kadam — Fri, 18 Oct 2019 05:36:33 GMT

@Anonymous while downgrading the plugin make sure that Fusion is closed. Close VS code once downgrade is done. Relaunch Fusion and check. This should work.

Thanks,

Rushikesh Kadam

Re: API debugger doesn't work after Oct 2019 update

cyberreefguru — Mon, 12 Oct 2020 13:39:45 GMT

Sudden Fusion won't open VS for me (yes, I have the correct extremely dated version of python selected) - this is relatively recent as it worked about a month ago.

Is there a fix for this issue yet? It's been a year - I have to be believe whatever bugs existed then have been fixed by now?

-Tom

Re: API debugger doesn't work after Oct 2019 update

pludikar — Mon, 12 Oct 2020 23:16:06 GMT

@cyberreefguru wrote:
...

- I have to be believe whatever bugs existed then have been fixed by now?

Nah. There have been too many bugs that I've reported that are still open, or at least, not obviously addressed. It's clearly more important for F360 to create new features than to spend time fixing basic foundational stuff.

Re: API debugger doesn't work after Oct 2019 update

JeromeBriot — Tue, 13 Oct 2020 06:24:01 GMT

Hello,

Close VS Code and Fusion 360.

Then remove the ms-python.python-XXXX.X.XXXXXX folders located in C:\Users\<USERNAME>\.vscode\extensions on Windows or /Users/<USERNAME>/.vscode/extensions on Mac

Open Fusion 360 and try to edit a script.

Re: API debugger doesn't work after Oct 2019 update

Anonymous — Wed, 11 Nov 2020 22:03:49 GMT

Hello,

I have an unorthodox beginners question. The aforementioned procedure worked perfectly for me. Yesterday. As of today Fusion 360 again fails to show me the source code in VSC. I followed the procedure several times. Without success.

ms-python.python-2019.9.34911 is the only installed version.

Can anybody help me with some advice ?

Re: API debugger doesn't work after Oct 2019 update

michael_koehle — Tue, 12 Oct 2021 17:58:14 GMT

Thanks for the solution. Can I suggest an actual video rather than a gif? There's no pausing a gif.