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

AppPath any other than ${workspaceRoot} freezes debugger #104

Open
Swiftwork opened this Issue Dec 13, 2016 · 7 comments

Comments

Projects
None yet
8 participants
@Swiftwork
Copy link

Swiftwork commented Dec 13, 2016

When appRoot isn't actually the workspace root but rather a sub directory "${workspaceRoot}/nativescript" the plugin won't get past the initialization call due to the server creating a socket hash from the workspaceRoot and not appRoot

@Swiftwork Swiftwork changed the title AppPath any other but ${workspaceRoot} freezes AppPath any other than ${workspaceRoot} freezes debugger Dec 13, 2016

@ivanbuhov

This comment has been minimized.

Copy link
Contributor

ivanbuhov commented Dec 14, 2016

@Swiftwork You are absolutely right. We have to think about another mechanism for calculating the unix socket path used for communication between the debug adapter and the extension host process.

@ivanbuhov ivanbuhov added the bug label Dec 14, 2016

@manojdcoder

This comment has been minimized.

Copy link

manojdcoder commented Feb 12, 2017

+1

1 similar comment
@Gyunikuchan

This comment has been minimized.

Copy link

Gyunikuchan commented May 4, 2017

+1

@stylefish

This comment has been minimized.

Copy link

stylefish commented Jun 26, 2017

anything new on this? i'm trying to develop a nativescript + electron desktop app with some code share and cannot let nativescript live inside the workspace folder. for now i'm using console.log() debugging ;)
so it would be nice to have this ;)
thanks for feedback!

@madmath03

This comment has been minimized.

Copy link

madmath03 commented Jul 30, 2017

+1

@harrijon

This comment has been minimized.

Copy link

harrijon commented Nov 17, 2017

+1

@5te1n

This comment has been minimized.

Copy link

5te1n commented Dec 6, 2017

I can't debug my plugin-seed, because of this issue. Is there already a fix for this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment