Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to Connect debugger to SBX #361

Open
jacobesplin opened this issue Jun 6, 2023 · 7 comments
Open

Unable to Connect debugger to SBX #361

jacobesplin opened this issue Jun 6, 2023 · 7 comments

Comments

@jacobesplin
Copy link

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:
Try to launch debugger

Expected behavior
The debugger should connect to the SBX

Screenshots
If applicable, add screenshots to help explain your problem.
image
The debugger hangs and does not produce any logs. I do have trace set to true.

Desktop (please complete the following information):

  • OS: Ubuntu 22.04.2 LTS x86 and Mac OS -> Monterey chip m1
  • VSCode version
  • Version: 1.78.2
    Date: 2023-05-10T14:47:05.613Z
    Electron: 22.5.2
    Chromium: 108.0.5359.215
    Node.js: 16.17.1
    V8: 10.8.168.25-electron.0
    OS: Linux x64 5.19.0-43-generic snap
    Sandboxed: Yes
  • The extension version [e.g. 22]
    latest

Additional context
I am not able to connect the debugger to my SBX using MAC or Ubuntu, but I am able to connect using windows 11. However, I am able to use dw-utils in every environment. I have tried to uninstall reinstall, changed workspace, tried different version with no avail.

@jacobesplin
Copy link
Author

Update: I was able to switch to an older version v1.4.33 and it is working on my Ubuntu and Mac. I just picked this one arbitrarily.

@SebastianBranZapata
Copy link

Update: I was able to switch to an older version v1.4.33 and it is working on my Ubuntu and Mac. I just picked this one arbitrarily.

I have the same problem, changing to version v1.4.33 works for me too.

@SqrTT
Copy link
Owner

SqrTT commented Jun 27, 2023

At this moment I have no found way to reproduce. Seems this happen mostly on Mac but non of Mac user I able to reach-out have this issue.
Could you please try to provide more info related to issue. For instance logs form Help -> Toggle Developer Tools or/and Output system sections (ie Main, Shared, Extension Host etc)?

@Renan-Costa-Sousa
Copy link

Switching to 1.4.33 works for me too. No version after that one works.

@bdion-pixel
Copy link

@SqrTT nothing in the dev tools. Starting with 1.4.34, Prophet no longer appears as an option under "Output". Not sure if that's helpful at all.

@bdion-pixel
Copy link

Btw, what changed from 1.4.33 to 1.4.34? There's a gap in the change log.

@bdion-pixel
Copy link

@SqrTT I just did some testing locally. At least for me, it appears to be the removal of the following lines from the package.json that causes the issue. After readding them and making no other changes, I can now use 1.4.40.
"onCommand:extension.prophet.command.create.cartridge", "workspaceContains:**/cartridge/*.properties",

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants