Skip to content

use only resource on kernel launcher #11339

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 3 commits into from
Apr 22, 2020

Conversation

DavidKutu
Copy link

For #11314

Also, I removed the comment to disable tslint and used ignoreErrors

  • Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
  • Title summarizes what is changing.
  • Has a news entry file (remember to thank yourself!).
  • Appropriate comments and documentation strings in the code.
  • Has sufficient logging.
  • Has telemetry for enhancements.
  • Unit tests & system/integration tests are added/updated.
  • Test plan is updated as appropriate.
  • package-lock.json has been regenerated by running npm install (if dependencies have changed).
  • The wiki is updated with any design decisions/details.

and instead use ignoreErrors
python interpreter, only a resource uri
@DavidKutu DavidKutu added the no-changelog No news entry required label Apr 22, 2020
@DavidKutu DavidKutu closed this Apr 22, 2020
@DavidKutu DavidKutu reopened this Apr 22, 2020
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities (and Security Hotspot 0 Security Hotspots to review)
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication


if (kernelSpec) {
// tslint:disable-next-line: no-floating-promises
this.writeCache(this.cache);
this.writeCache(this.cache).ignoreErrors();
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@codecov-io
Copy link

codecov-io commented Apr 22, 2020

Codecov Report

Merging #11339 into master will decrease coverage by 0.07%.
The diff coverage is 100.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master   #11339      +/-   ##
==========================================
- Coverage   61.05%   60.98%   -0.08%     
==========================================
  Files         604      606       +2     
  Lines       33421    33448      +27     
  Branches     4732     4730       -2     
==========================================
- Hits        20405    20398       -7     
- Misses      12575    12605      +30     
- Partials      441      445       +4     
Impacted Files Coverage Δ
...client/datascience/kernel-launcher/kernelFinder.ts 61.45% <100.00%> (-17.55%) ⬇️
src/datascience-ui/react-common/arePathsSame.ts 75.00% <0.00%> (-12.50%) ⬇️
src/client/common/utils/platform.ts 64.70% <0.00%> (-11.77%) ⬇️
src/client/datascience/debugLocationTracker.ts 76.56% <0.00%> (-1.57%) ⬇️
src/client/activation/activationService.ts 87.35% <0.00%> (-0.88%) ⬇️
src/client/activation/serviceRegistry.ts 82.71% <0.00%> (-0.83%) ⬇️
src/client/common/process/proc.ts 14.49% <0.00%> (-0.73%) ⬇️
...lient/activation/languageServer/analysisOptions.ts 59.59% <0.00%> (-0.57%) ⬇️
src/client/activation/node/manager.ts 27.77% <0.00%> (ø)
... and 4 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 00c2229...5db4a94. Read the comment docs.

Copy link

@rchiodo rchiodo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

@DavidKutu DavidKutu merged commit b8fd21c into master Apr 22, 2020
@DavidKutu DavidKutu deleted the davidkutu/useOnlyResourceOnKernelLauncher branch April 22, 2020 21:30
@lock lock bot locked as resolved and limited conversation to collaborators May 5, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
no-changelog No news entry required
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants