Skip to content

Revert change to canUseEvents in IoSessionOptions#22791

Merged
1 commit merged intomasterfrom
canUseEvents
Mar 22, 2018
Merged

Revert change to canUseEvents in IoSessionOptions#22791
1 commit merged intomasterfrom
canUseEvents

Conversation

@ghost
Copy link
Copy Markdown

@ghost ghost commented Mar 22, 2018

Fixes #22790 (tested in a local build with vscode)
In #22591 this was changed from hardcoded true to eventPort !== undefined.

@amcasey
Copy link
Copy Markdown
Member

amcasey commented Mar 22, 2018

  1. Oops
  2. How does VS Code get events without using eventPort?
  3. Can we eliminate the flag altogether if it's always true?

@mhegazy
Copy link
Copy Markdown
Contributor

mhegazy commented Mar 22, 2018

How does VS Code get events without using eventPort?

eventPort is rely a VS construct to avoid needing to handle async events on the same io channel as sync messages

Can we eliminate the flag altogether if it's always true?

yes.. probably..

@ghost ghost merged commit 67670d8 into master Mar 22, 2018
@ghost ghost deleted the canUseEvents branch March 22, 2018 17:29
@ghost
Copy link
Copy Markdown
Author

ghost commented Mar 22, 2018

yes.. probably..

That option is public though.

@mhegazy
Copy link
Copy Markdown
Contributor

mhegazy commented Mar 22, 2018

humm.. @aozgaa looked into this a while back.. i think he might know more.

@microsoft microsoft locked and limited conversation to collaborators Jul 25, 2018
This pull request was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants