Skip to content

fix: fix waitForDebugger handling #1073

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

Merged
merged 1 commit into from
Feb 6, 2019
Merged

Conversation

DimitarTachev
Copy link
Contributor

PR Checklist

What is the current behavior?

After the 5.1.1 releases of the CLI and the Runtime, the CLI is always sending AttachRequest before a debug session which is clearing the listenSource. In this way, the app is resumed and the --debug-brk flag is not working properly.

What is the new behavior?

In order to avoid that, we do not resume the app when closing the listening source anymore. It will be resumed only when a debugging client is attached or when the 30 secs timeout is reached.

After the 5.1.1 releases of the CLI and the Runtime, the CLI is always sending `AttachRequest` before a debug session which is clearing the `listenSource`. In this way, the app is resumed and the `--debug-brk` flag is not working properly. 

In order to avoid that, we do not resume the app when closing the listening source anymore. It will be resumed only when a debugging client is attached or the 30 secs timeout is reached.
@mbektchiev mbektchiev self-assigned this Feb 6, 2019
@mbektchiev mbektchiev self-requested a review February 6, 2019 14:08
@vtrifonov vtrifonov merged commit a8fe71e into master Feb 6, 2019
@vtrifonov vtrifonov deleted the tachev/fix-wait-for-debugger branch February 6, 2019 15:00
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

Successfully merging this pull request may close these issues.

4 participants