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

switch to execSync to ensure that no install requests are interleaved #12259

Merged
merged 1 commit into from
Nov 15, 2016

Conversation

vladima
Copy link
Contributor

@vladima vladima commented Nov 15, 2016

// CC @mhegazy, @billti

Currently typings installer processes requests one by one and runs installation asyncronously. Cache of installed typings is updated after npm install is done. This means that there might be an interesting situation when installer receives two requests in a row to install typings for different projects. After first request installer will discover that typings are not yet there and will kick off npm install. However if second request will come before npm install is completed then installer will think that typings are not installed and will run second instance of npm install process. Simplest way to deal with this issue is to switch npm install to be synchronous so all requests are processed serially.

@vladima vladima merged commit 3a094e7 into release-2.0.5 Nov 15, 2016
@vladima vladima deleted the vladima/use-exec-sync branch November 15, 2016 19:00
vladima added a commit that referenced this pull request Nov 15, 2016
* treat failures to resolve module name as missing packages (#12237)

* added extra check to prevent multiple installation of the same typing, added version field to telemetry event (#12258)

* added extra check to prevent multiple installation of the same typing, added version field to telemetry event

* use ts.version

* switch to execSync to ensure that no install orders are interleaved (#12259)

* Make sure version is public

* Update file with version string for nightly release
@microsoft microsoft locked and limited conversation to collaborators Jun 19, 2018
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.

3 participants