Stopping the server or reconnecting without killing Fusion

[TRIALCAD2014]

every now and then, sometimes 10 times a day when I try to run a script in debug I get this message.

WHen I click Cancel the server stop button in VS is  not available. In Fusion I can still run the script but if If I try to re-launch in debug I get the same message.
Only stopping and restarting Fusion works ut there must be a less dramatic way to either reattach or stop it. 
I even tried to hunt down the pid but nothing worked.

Thank you,
Adrian

[kandennti]

Hi @TRIALCAD2014 .

I would like to know how to do it too.
In the end, the only way I can figure out how to fix it is to restart Fusion360.

[j.han97]

What happened before this error? 

From my experience there usually are two reasons:

1. The add-in is still running and I tried to run the add-in again.

2. There is another script/add-in in debug mode.

 I'm interested in experimenting with this if you can provide a way/description to reproduce your exact situation.

[TRIALCAD2014]

I modified my setting to
{
"version": "0.2.0",
"configurations": [
        {
"name": "Python: Attach using Process Id",
"type": "python",
"request": "attach",
"processId": "${command:pickProcess}"
        },
        {
"name": "Python: Attach",
"type": "python",
"request": "attach",
"pathMappings": [
                {
"localRoot": "${workspaceRoot}",
"remoteRoot": "${workspaceRoot}"
                }
            ],
"osx": {
"filePath": "${file}"
            },
"windows": {
"filePath": "${file}"
            },
"port": 9000,
"host": "localhost"
        }
    ]
}

and then I tried to run that select the existing PID. That should work
but so far for me no luck.

[TRIALCAD2014]

I do not recall a consistent scenario. It usually happens when I switch
back between the VS debug and Fusion interface while some code is still
executing.

I think VS thinks server is stopped when the Fusion server becomes
unresponsive. At that point SV abandons showing the disconnect double
link in the menu.

[j.han97]

I see. I don't think my experience can relate to your matter unfortunately.  

Have you tried re-attaching from Fusion 360? Since you mentioned that you can run the script in F360, I assume that it is alive (responding). I would try debugging the script (click Edit instead of Run) from F360 again to re-attach them. 

[TRIALCAD2014]

"I would try debugging the script (click Edit instead of Run) from F360 again to re-attach them. "

Well.. the second screen capture shows what you get when you try that.
As I mentioned, I can still normally run the script from Fusion .
Thank you for trying to look into it 🙂

[j.han97]

I have never met this situation before... Seems like I have not spent enough time working with Fusion 360 (fortunately)