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

Add setting to control speed of diagnostic publishing #2357

Merged
merged 39 commits into from
Aug 9, 2018
Merged

Add setting to control speed of diagnostic publishing #2357

merged 39 commits into from
Aug 9, 2018

Conversation

MikhailArkhipov
Copy link

@MikhailArkhipov MikhailArkhipov commented Aug 9, 2018

Fixes #2270

  • Title summarizes what is changing
  • Includes a news entry file (remember to thank yourself!)
  • Unit tests & code coverage are not adversely affected (within reason)
  • Works on all actively maintained versions of Python (e.g. Python 2.7 & the latest Python 3 release)
  • Works on Windows 10, macOS, and Linux (e.g. considered file system case-sensitivity)

microsoft/PTVS#4612

Copy link

@d3r3kk d3r3kk left a comment

Choose a reason for hiding this comment

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

Looks just fine 👍, but let's add a few tests before we submit...

@codecov
Copy link

codecov bot commented Aug 9, 2018

Codecov Report

Merging #2357 into master will increase coverage by 0.14%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #2357      +/-   ##
==========================================
+ Coverage   75.98%   76.13%   +0.14%     
==========================================
  Files         309      309              
  Lines       14341    14341              
  Branches     2540     2540              
==========================================
+ Hits        10897    10918      +21     
+ Misses       3434     3413      -21     
  Partials       10       10
Flag Coverage Δ
#MacOS 74.17% <100%> (ø) ⬆️
#Windows 74.33% <100%> (+0.06%) ⬆️
Impacted Files Coverage Δ
src/client/activation/languageServer.ts 26.08% <100%> (ø) ⬆️
src/client/linters/lintingEngine.ts 91.15% <0%> (-0.89%) ⬇️
src/client/linters/baseLinter.ts 95.78% <0%> (+6.31%) ⬆️
src/client/common/application/applicationShell.ts 30.76% <0%> (+7.69%) ⬆️
src/client/common/logger.ts 68.42% <0%> (+10.52%) ⬆️
src/client/linters/errorHandlers/errorHandler.ts 100% <0%> (+22.22%) ⬆️
src/client/linters/errorHandlers/notInstalled.ts 100% <0%> (+55.55%) ⬆️

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 c3a04cd...d7cd632. Read the comment docs.

@MikhailArkhipov
Copy link
Author

Tests for the delay? We'll add those to LS repo when Alex is done porting tests.

@MikhailArkhipov
Copy link
Author

microsoft/PTVS#4612

@d3r3kk
Copy link

d3r3kk commented Aug 9, 2018

Tests for the delay? We'll add those to LS repo when Alex is done porting tests.

I'm not worried about the delay, this is only a config change. Please pardon my unfamiliarity with how the LS gets it's config settings, I had assumed that VSCode-Python sets them into the LS at some point in the code.

My request for tests would simply to be 'Check that the value set in the config is being sent to the LS', but perhaps that is read directly from our package by the LS itself?

@MikhailArkhipov
Copy link
Author

@d3r3kk
Copy link

d3r3kk commented Aug 9, 2018

Good to know, thanks!

@MikhailArkhipov MikhailArkhipov merged commit 9c078c0 into microsoft:master Aug 9, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Jul 31, 2019
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.

Provide the ability to turn off live error reporting in the new language server
3 participants