Debugger not starts up (with no errors or messages)

[vrushali-desai]

Prophet Debugger is not working for me as expected since past few days. When I click on the run I always get a popup asking to select the environment (screenshot attached below). Nothing happens after selecting the environment.

It was working fine before. I have tried also by disabling other extensions, closing VSCode completely but nothing seems to help. The debugger sometimes works properly after I reboot the system. I am on

• OS: macOS Catalina
• VSCode version - 1.40.2
• The extension version - 1.2.4

[ctwh]

Experiencing same problem. @SqrTT any updates? I think currently I am relegated to using Eclipse when needing to debug.

[SqrTT]

I'm not able to reproduce. Could you guys provide more detailed info/steps? Is the issue reproducible for older versions? Any logs/errors? Try to reinstall the extension.

[vrushali-desai]

Strangely the debugger is working for me now. Although I cannot say for sure what fixed the debugger; but one thing is that now it's started working after I save my projects in workspace. Of course I had tried it before also but had not worked; also I could use the debugger previously without having a workspace and yes, had done the reinstallation of the extension several times before posting the issue. Nevertheless, I am happy that it's working for me now as even I was considering moving to eclipse to be able to debug.

[isabelklings]

I still have this issue. Debug console error message:

Error
 Error
    at Request._callback (###\.vscode\extensions\sqrtt.prophet-1.2.4\out\Connection.js:73:35)
    at Request.self.callback (###\.vscode\extensions\sqrtt.prophet-1.2.4\node_modules\request\request.js:185:22)
    at Request.emit (events.js:200:13)
    at Request.<anonymous> (###\.vscode\extensions\sqrtt.prophet-1.2.4\node_modules\request\request.js:1161:10)
    at Request.emit (events.js:200:13)
    at IncomingMessage.<anonymous> (###\.vscode\extensions\sqrtt.prophet-1.2.4\node_modules\request\request.js:1083:12)
    at Object.onceWrapper (events.js:288:20)
    at IncomingMessage.emit (events.js:205:15)
    at endReadableNT (_stream_readable.js:1154:12)
    at processTicksAndRejections (internal/process/task_queues.js:84:9)Disconnecting...
Error

I installed previous VS Code version, previous Prophet version, I created a new workspace and I had no success.

[SqrTT]

could you please try to uncheck extension.prophet.sandbox.filesystem.enabled = false

and remove Sandbox File system workspace, and see if debugger works after that?

[isabelklings]

could you please try to uncheck extension.prophet.sandbox.filesystem.enabled = false

and remove Sandbox File system workspace, and see if debugger works after that?

Unfortunately it's not working :( Do you have another idea maybe? Thank you!

[ctwh]

@SqrTT That seemed to work for me.

[bradbrock]

I'm also experiencing the issue. setting extension.prophet.sandbox.filesystem.enabled=false did not resolve the problem.

[SqrTT]

@bradbrock Have you tried to remove Sandbox File system workspace?

[bradbrock]

@SqrTT I haven't, but the issue seems to have worked itself out. My sandbox was restarted from control center and everything has been working as expected since then.

[sghata]

I'm also experiencing the same issue. The debugger stops working, and I get the following: even though I have the launch.json file. When I hit "create a launch.json file", I get the following error:

Unable to create 'launch.json' file inside the '.vscode' folder (Unable to write file (EntryNotFound (FileSystemError): ccfs://current-sandbox/.vscode)).

The way I'm currently fixing it is by uninstalling prophet, restarting vscode, and then installing it again. The issue seems to happens once every few days but I've not seen a pattern or a way to reproduce it.

[SqrTT]

@sghata Have you tried to disable sandbox filesystem and remove it from workspace, like described above?

[cgornez]

Hi, I am also experiencing this today.

I've already disabled the sandbox filesystem but it's not working for me.

[SqrTT]

Hello all.

This ticket has 3 totally different issues:

1. debugger doesn't start with no error (or messages) in debug console.
2. Can't create configuration launch.json (Unable to write file (EntryNotFound (FileSystemError): ccfs://current-sandbox/.vscode)).
3. debugger starts with error in debug console.

So, let's process as different issues.

1. Unfortunately, I'm not able reproduce an issue, need more details, log, etc.
2. remove sandbox file system should help.
3. let's track in #224

[jmatos]

I'm also having the issue with the debugger not working - no error message at all. In vscode I notice that the progress animation that appears when you click on the Run arrow or press F5 never stops. Is there a way to see what is going on via logs?

[jmatos]

I'm also having the issue with the debugger not working - no error message at all. In vscode I notice that the progress animation that appears when you click on the Run arrow or press F5 never stops. Is there a way to see what is going on via logs?

[SqrTT]

do you have installed a plugin ~LiveSearch~ LiveShare ? like in #147 ?

[SqrTT]

is issue reproducible if all other plugins are disabled?

[jmatos]

I disabled all plugins and I'm still not able to debug :(

[jmatos]

I got it working again - I disabled the Prophet extension and then enabled it but this time I chose the "Enable (Workspace)" option instead of "Enable" - not sure why this made a difference but I'm happy now!

[jmatos]

I spoke too soon - its not working again :(

[jmatos]

Any other ideas? The debugging feature in eclipse does work for me - that seems to indicate that it is an issue with the plugin or with vscode. Am I the only one using a MAC that is having issues with debugging?

[jmatos]

I guess its back to eclipse :(

[jmatos]

Uninstalled vscode and installed vscode insiders and now debugging is working again.

https://code.visualstudio.com/insiders/

[SqrTT]

vscode and vscode insiders use the same version of the extension...

[ValentinGurkov]

For me, restarts of VSCode have always fixed the debugger not starting. I'm not sure this problem is related to the extension.

[vlad-simion]

The debugger is not stopping the code on breakpoints without any error. After restarting the VS multiple times debugger works but then the auto-upload is not working anymore. I need to use the command Enable Upload for any change.

OS: macOS Catalina VSCode version - 1.54.3 The extension version - 1.4.15

[SqrTT]

Hi @vlad-simion How long this is happening? Does it happen with previous versions? Could you please try to previous version? Are you sure code is executed where breakpoints is set? Let's say if add loging to file does log records appears? Is cache enabled on sandbox?

PS. seems you issue is not related to current ticket. Would be nice to not mix all issue into one and report it as separate

[vlad-simion]

Hi @vlad-simion How long this is happening? Does it happen with previous versions? Could you please try to previous version? Are you sure code is executed where breakpoints is set? Let's say if add loging to file does log records appears? Is cache enabled on sandbox?

PS. seems you issue is not related to current ticket. Would be nice to not mix all issue into one and report it as separate

I found my issue. It looks like a git repository inside a cartridge broke the Prophet. Once I removed the repository files the Prophet worked again as expected.

[basitafzal-omnicom]

I had the same issue "debugger tries to initiate but goes away". The reason behind this was my outdated credentials in dw.json file. It wasn't any issue with the VS Code or Prophet Debugger. Just sharing if it could help anyone else as well.