text:
id when creating new Mongo doc must be string of 12 bytes or 24 hex characters

Repro steps:

Open explorer on a mongo account
Create a new doc
Enter 'jing' as the id
Open the doc
Edit the doc
Update to Azure

Expected: Update succeeds
Actual: "Error: Argument passed in must be a single String of 12 bytes or a string of 24 hex characters"

Maybe we shouldn't let the user specify an id for new mongo docs? It seems like it has to be something like '59c2907ea7c5c4215637d9fd' every time

repo: Microsoft/vscode-cosmosdb


text:
Slowdown on code assist with eslint enabled

Just recently, I've been experiencing some issues with medium-sized javascript files with Redux.js action creation and dispatching-type code. I've tried installing the nightly build version of VSCode to see if it may have been something related to the latest stable version of VSCode. I've disabled a number of extensions, as well as the github integration. These had a marginal impact on performance. Disabling ESlint for my workspace, however, seemed to resolve the performance issue.

@benduran are you able to share your project. ESLint runs in a complete separate process than the JS code assist. I would like to understand why/how ESLint affects the JS code assist. Do you have high CPU load ?

@dbaeumer I may be able to share the specific file in question, but not the whole project, as it is a work-related project and contains sensitive information and features we cannot share with the public at the moment. I will try running a CPU profiler on VSCode while running my project and report back later this afternoon / early evening.

I'm experiencing the same issue. I enabled the ESLint extension (dbaeumer.vscode-eslint) a few weeks ago and set {"eslint.autoFixOnSave": true}. Ever since, I quite frequently run into significant lag with code assist and often with vscode as a whole.
The lag becomes so noticeable that characters appear a solid second or two after I type them. After a while of increasing lag, the autoFixOnSave stops working altogether (although it doesn't throw any errors, it just stops fixing issues on save). ESLint will still detect and report on issues it finds though. When ESLint finally gives up it often clears up the lag along with it, but not always. Restarting vscode is the only way to clear it up.
The output window from ESLint only shows the following. I'll turn on verbose messages to see if anything stands out over the next few days.
[Info  - 1:29:15 PM] ESLint server is running.
[Info  - 1:29:28 PM] ESLint library loaded from: /Users/mark/repos/scout-client/node_modules/eslint/lib/api.js

So far this issue hasn't been restricted to one particular project for me either. I've noticed it while working on React, Ember and Node apps of various sizes.
Happy to help further if you need other specific details.

@mwadden Thanks for chiming. I've been so busy at work that I haven't had time to run my CPU profile. I found that by switching to this: "eslint.run": "onSave" corrects my issue. It is really only noticeable when "eslint.run": "onType" is set (which it is by default)

@benduran I have an idea what could cause this since it becomes more responsice for onSave. Will look into this beginning of April.

@dbaeumer Thanks for checking into this. I'm glad I have a temporary work around for this issue, but I look forward to hearing more about a possible fix 👍

@dlong500 @benduran I worked on a new version of the ESLint extension that uses a more sophisticated validation queue. It will allow for even tweak the timeouts if necessary.
Since the change is bigger and it might not even fix the problems you are seeing I would like to ask you to beta test the version. To do so following these steps:

download
vscode-eslint-1.2.9.zip
rename it to .vsix
install it using the code / code-insider command from a terminal. For example code --install-extension vscode-eslint-1.2.9.vsix
use it and let me know if it improves the behavior.

IMPORTANT: since you installed the extension using an explicit command the extension will not be auto updated from the store anymore. When I push 1.2.9 (which I will let you know in this issue) then you need to uninstall the ESLint extension and reinstall from the store. Sorry for this inconvenience.

Thanks.  I'll test it out over the next few days and let you know how it goes.

I've installed it tonight. Will test it thoroughly between now and end of
the week. Will report back with my findings
On Tue, Apr 4, 2017 at 12:43 PM, Davison Long notifications@github.com
wrote:

Thanks. I'll test it out over the next few days and let you know how it
goes.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode-eslint/issues/215#issuecomment-291610586,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGGJn917D7BJPcUJJn82x33Qv3Hy220yks5rsp1rgaJpZM4McF6q
.

--

Benjamin

@dbaeumer I've been using the eslint build you prepped. I can confirm that it no longer affects intellisense while coding. Code assist is snappy like it was previously. However, some of my files do cause noticeable performance issues with the linting messages I receive in the eslint console in VS Code. The linter does eventually catch up, however, it is a bit sluggish. There are two files in question that cause this slowdown, but they're relatively small (one is less than 700 lines, the other is less than 300 lines).

I've been having a similar issue with eslint in vs code -- sometimes it takes a very long time to catch up with linting a file that is being edited. Right now I am working on refactoring a ~2000 line file, so it is particularly noticeable, but it used to not be a problem 😕
The messages trace looks somewhat like this:
[Trace - 5:28:31 PM] Received notification 'eslint/status'.
[Trace - 5:28:31 PM] Received response 'textDocument/codeAction - (74)' in 13113ms.
[Trace - 5:28:32 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 5:28:32 PM] Received notification 'eslint/status'.
[Trace - 5:28:33 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 5:28:33 PM] Received notification 'eslint/status'.
[Trace - 5:28:33 PM] Received response 'textDocument/codeAction - (75)' in 15462ms.
[Trace - 5:28:33 PM] Received response 'textDocument/codeAction - (76)' in 15386ms.
[Trace - 5:28:34 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 5:28:34 PM] Received notification 'eslint/status'.
[Trace - 5:28:35 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 5:28:35 PM] Received notification 'eslint/status'.
[Trace - 5:28:35 PM] Received response 'textDocument/codeAction - (77)' in 17411ms.
[Trace - 5:28:35 PM] Received response 'textDocument/codeAction - (78)' in 17221ms.
[Trace - 5:28:36 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 5:28:36 PM] Received notification 'eslint/status'.
[Trace - 5:28:37 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 5:28:37 PM] Received notification 'eslint/status'.
[Trace - 5:28:37 PM] Received response 'textDocument/codeAction - (79)' in 19010ms.
[Trace - 5:28:37 PM] Received response 'textDocument/codeAction - (80)' in 18993ms.
[Trace - 5:28:38 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 5:28:38 PM] Received notification 'eslint/status'.
[Trace - 5:28:38 PM] Received response 'textDocument/codeAction - (81)' in 19838ms.
[Trace - 5:28:38 PM] Received response 'textDocument/codeAction - (82)' in 19675ms.
[Trace - 5:28:39 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 5:28:39 PM] Received notification 'eslint/status'.
[Trace - 5:28:40 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 5:28:40 PM] Received notification 'eslint/status'.
[Trace - 5:28:40 PM] Received response 'textDocument/codeAction - (83)' in 20812ms.
[Trace - 5:28:40 PM] Received response 'textDocument/codeAction - (84)' in 20693ms.

Often, when it starts lagging behind, the delays just keep getting larger and larger (while at 100% CPU) until I stop editing, at which point after several seconds the delays start getting shorter until it is done.
I have tried the build linked by @dbaeumer but the performance problem did not change.

@Kovensky thanks a lot for the trace. Would you be able to include the whole trace. To really understand what is going on I need to see the change notifications send from the client as well. They show up as Sending notification ... in the trace.
@benduran could you produce such a trace as well. To do so enable the setting "eslint.trace.server": "messages"
One thing that the trace shows is that there are two many textDocument/codeAction requests. These need to be queued better as well.

I disabled and re-enabled eslint usinc ⌘+Shift+P, waited until the output stopped, cleared the output, and then wrote (const thread of threads) {ENTER (continuation of a for statement head). This is the full output at that point:
[Trace - 7:12:35 PM] Sending notification 'textDocument/didChange'.
[Trace - 7:12:35 PM] Sending request 'textDocument/codeAction - (15)'.
[Trace - 7:12:35 PM] Sending request 'textDocument/codeAction - (16)'.
[Trace - 7:12:35 PM] Received response 'textDocument/codeAction - (15)' in 3ms.
[Trace - 7:12:35 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 7:12:35 PM] Received response 'textDocument/codeAction - (16)' in 138ms.
[Trace - 7:12:35 PM] Sending notification 'textDocument/didChange'.
[Trace - 7:12:35 PM] Sending request 'textDocument/codeAction - (17)'.
[Trace - 7:12:35 PM] Sending request 'textDocument/codeAction - (18)'.
[Trace - 7:12:35 PM] Received response 'textDocument/codeAction - (17)' in 7ms.
[Trace - 7:12:35 PM] Sending request 'textDocument/codeAction - (19)'.
[Trace - 7:12:35 PM] Sending request 'textDocument/codeAction - (20)'.
[Trace - 7:12:35 PM] Sending notification 'textDocument/didChange'.
[Trace - 7:12:35 PM] Sending request 'textDocument/codeAction - (21)'.
[Trace - 7:12:35 PM] Sending request 'textDocument/codeAction - (22)'.
[Trace - 7:12:35 PM] Sending notification 'textDocument/didChange'.
[Trace - 7:12:35 PM] Sending request 'textDocument/codeAction - (23)'.
[Trace - 7:12:35 PM] Sending request 'textDocument/codeAction - (24)'.
[Trace - 7:12:35 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 7:12:35 PM] Received response 'textDocument/codeAction - (18)' in 156ms.
[Trace - 7:12:35 PM] Received response 'textDocument/codeAction - (19)' in 148ms.
[Trace - 7:12:35 PM] Received response 'textDocument/codeAction - (20)' in 148ms.
[Trace - 7:12:35 PM] Sending request 'textDocument/codeAction - (25)'.
[Trace - 7:12:35 PM] Sending request 'textDocument/codeAction - (26)'.
[Trace - 7:12:36 PM] Sending notification 'textDocument/didChange'.
[Trace - 7:12:36 PM] Sending request 'textDocument/codeAction - (27)'.
[Trace - 7:12:36 PM] Sending request 'textDocument/codeAction - (28)'.
[Trace - 7:12:36 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 7:12:36 PM] Sending request 'textDocument/codeAction - (29)'.
[Trace - 7:12:36 PM] Sending request 'textDocument/codeAction - (30)'.
[Trace - 7:12:36 PM] Received response 'textDocument/codeAction - (21)' in 376ms.
[Trace - 7:12:36 PM] Received response 'textDocument/codeAction - (22)' in 375ms.
[Trace - 7:12:36 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 7:12:36 PM] Received response 'textDocument/codeAction - (23)' in 445ms.
[Trace - 7:12:36 PM] Received response 'textDocument/codeAction - (24)' in 441ms.
[Trace - 7:12:36 PM] Received response 'textDocument/codeAction - (25)' in 411ms.
[Trace - 7:12:36 PM] Received response 'textDocument/codeAction - (26)' in 410ms.
[Trace - 7:12:36 PM] Sending notification 'textDocument/didChange'.
[Trace - 7:12:36 PM] Sending notification 'textDocument/didChange'.
[Trace - 7:12:36 PM] Sending request 'textDocument/codeAction - (31)'.
[Trace - 7:12:36 PM] Sending request 'textDocument/codeAction - (32)'.
[Trace - 7:12:36 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 7:12:36 PM] Received response 'textDocument/codeAction - (27)' in 515ms.
[Trace - 7:12:36 PM] Received response 'textDocument/codeAction - (28)' in 512ms.
[Trace - 7:12:36 PM] Received response 'textDocument/codeAction - (29)' in 385ms.
[Trace - 7:12:36 PM] Received response 'textDocument/codeAction - (30)' in 385ms.
[Trace - 7:12:36 PM] Sending request 'textDocument/codeAction - (33)'.
[Trace - 7:12:36 PM] Sending request 'textDocument/codeAction - (34)'.
[Trace - 7:12:36 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 7:12:36 PM] Sending notification 'textDocument/didChange'.
[Trace - 7:12:36 PM] Sending request 'textDocument/codeAction - (35)'.
[Trace - 7:12:36 PM] Sending request 'textDocument/codeAction - (36)'.
[Trace - 7:12:36 PM] Sending notification 'textDocument/didChange'.
[Trace - 7:12:36 PM] Sending request 'textDocument/codeAction - (37)'.
[Trace - 7:12:36 PM] Sending request 'textDocument/codeAction - (38)'.
[Trace - 7:12:36 PM] Sending notification 'textDocument/didChange'.
[Trace - 7:12:36 PM] Sending request 'textDocument/codeAction - (39)'.
[Trace - 7:12:36 PM] Sending request 'textDocument/codeAction - (40)'.
[Trace - 7:12:36 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 7:12:36 PM] Received response 'textDocument/codeAction - (31)' in 245ms.
[Trace - 7:12:36 PM] Received response 'textDocument/codeAction - (32)' in 245ms.
[Trace - 7:12:36 PM] Received response 'textDocument/codeAction - (33)' in 238ms.
[Trace - 7:12:36 PM] Received response 'textDocument/codeAction - (34)' in 238ms.
[Trace - 7:12:36 PM] Sending request 'textDocument/codeAction - (41)'.
[Trace - 7:12:36 PM] Sending request 'textDocument/codeAction - (42)'.
[Trace - 7:12:36 PM] Sending notification 'textDocument/didChange'.
[Trace - 7:12:36 PM] Sending request 'textDocument/codeAction - (43)'.
[Trace - 7:12:36 PM] Sending request 'textDocument/codeAction - (44)'.
[Trace - 7:12:36 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 7:12:36 PM] Received response 'textDocument/codeAction - (35)' in 232ms.
[Trace - 7:12:36 PM] Received response 'textDocument/codeAction - (36)' in 231ms.
[Trace - 7:12:36 PM] Sending request 'textDocument/codeAction - (45)'.
[Trace - 7:12:36 PM] Sending request 'textDocument/codeAction - (46)'.
[Trace - 7:12:36 PM] Sending notification 'textDocument/didChange'.
[Trace - 7:12:36 PM] Sending request 'textDocument/codeAction - (47)'.
[Trace - 7:12:36 PM] Sending request 'textDocument/codeAction - (48)'.
[Trace - 7:12:37 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 7:12:37 PM] Received response 'textDocument/codeAction - (37)' in 339ms.
[Trace - 7:12:37 PM] Received response 'textDocument/codeAction - (38)' in 333ms.
[Trace - 7:12:37 PM] Sending request 'textDocument/codeAction - (49)'.
[Trace - 7:12:37 PM] Sending request 'textDocument/codeAction - (50)'.
[Trace - 7:12:37 PM] Sending notification 'textDocument/didChange'.
[Trace - 7:12:37 PM] Sending request 'textDocument/codeAction - (51)'.
[Trace - 7:12:37 PM] Sending request 'textDocument/codeAction - (52)'.
[Trace - 7:12:37 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 7:12:37 PM] Received response 'textDocument/codeAction - (39)' in 343ms.
[Trace - 7:12:37 PM] Received response 'textDocument/codeAction - (40)' in 342ms.
[Trace - 7:12:37 PM] Received response 'textDocument/codeAction - (41)' in 321ms.
[Trace - 7:12:37 PM] Received response 'textDocument/codeAction - (42)' in 320ms.
[Trace - 7:12:37 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 7:12:37 PM] Received response 'textDocument/codeAction - (43)' in 388ms.
[Trace - 7:12:37 PM] Received response 'textDocument/codeAction - (44)' in 387ms.
[Trace - 7:12:37 PM] Received response 'textDocument/codeAction - (45)' in 321ms.
[Trace - 7:12:37 PM] Received response 'textDocument/codeAction - (46)' in 321ms.
[Trace - 7:12:37 PM] Sending notification 'textDocument/didChange'.
[Trace - 7:12:37 PM] Sending request 'textDocument/codeAction - (53)'.
[Trace - 7:12:37 PM] Sending request 'textDocument/codeAction - (54)'.
[Trace - 7:12:37 PM] Sending notification 'textDocument/didChange'.
[Trace - 7:12:37 PM] Sending request 'textDocument/codeAction - (55)'.
[Trace - 7:12:37 PM] Sending request 'textDocument/codeAction - (56)'.
[Trace - 7:12:37 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 7:12:37 PM] Received response 'textDocument/codeAction - (47)' in 377ms.
[Trace - 7:12:37 PM] Received response 'textDocument/codeAction - (48)' in 375ms.
[Trace - 7:12:37 PM] Received response 'textDocument/codeAction - (49)' in 318ms.
[Trace - 7:12:37 PM] Received response 'textDocument/codeAction - (50)' in 317ms.
[Trace - 7:12:37 PM] Sending request 'textDocument/codeAction - (57)'.
[Trace - 7:12:37 PM] Sending request 'textDocument/codeAction - (58)'.
[Trace - 7:12:37 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 7:12:37 PM] Received response 'textDocument/codeAction - (51)' in 440ms.
[Trace - 7:12:37 PM] Received response 'textDocument/codeAction - (52)' in 439ms.
[Trace - 7:12:37 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 7:12:37 PM] Received response 'textDocument/codeAction - (53)' in 328ms.
[Trace - 7:12:37 PM] Received response 'textDocument/codeAction - (54)' in 327ms.
[Trace - 7:12:37 PM] Sending notification 'textDocument/didChange'.
[Trace - 7:12:37 PM] Sending notification 'textDocument/didChange'.
[Trace - 7:12:37 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 7:12:37 PM] Received response 'textDocument/codeAction - (55)' in 351ms.
[Trace - 7:12:37 PM] Received response 'textDocument/codeAction - (56)' in 350ms.
[Trace - 7:12:37 PM] Received response 'textDocument/codeAction - (57)' in 287ms.
[Trace - 7:12:37 PM] Received response 'textDocument/codeAction - (58)' in 287ms.
[Trace - 7:12:37 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 7:12:37 PM] Sending request 'textDocument/codeAction - (59)'.
[Trace - 7:12:37 PM] Sending request 'textDocument/codeAction - (60)'.
[Trace - 7:12:37 PM] Sending request 'textDocument/codeAction - (61)'.
[Trace - 7:12:37 PM] Sending request 'textDocument/codeAction - (62)'.
[Trace - 7:12:37 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 7:12:37 PM] Received response 'textDocument/codeAction - (59)' in 90ms.
[Trace - 7:12:37 PM] Received response 'textDocument/codeAction - (60)' in 89ms.
[Trace - 7:12:37 PM] Received response 'textDocument/codeAction - (61)' in 82ms.
[Trace - 7:12:37 PM] Received response 'textDocument/codeAction - (62)' in 81ms.
[Trace - 7:12:37 PM] Sending request 'textDocument/codeAction - (63)'.
[Trace - 7:12:37 PM] Sending request 'textDocument/codeAction - (64)'.
[Trace - 7:12:37 PM] Received response 'textDocument/codeAction - (63)' in 1ms.
[Trace - 7:12:37 PM] Received response 'textDocument/codeAction - (64)' in 0ms.
[Trace - 7:12:37 PM] Sending notification 'textDocument/didChange'.
[Trace - 7:12:37 PM] Sending request 'textDocument/codeAction - (65)'.
[Trace - 7:12:37 PM] Sending request 'textDocument/codeAction - (66)'.
[Trace - 7:12:37 PM] Received response 'textDocument/codeAction - (65)' in 4ms.
[Trace - 7:12:38 PM] Sending notification 'textDocument/didChange'.
[Trace - 7:12:38 PM] Sending request 'textDocument/codeAction - (67)'.
[Trace - 7:12:38 PM] Sending request 'textDocument/codeAction - (68)'.
[Trace - 7:12:38 PM] Sending notification 'textDocument/didChange'.
[Trace - 7:12:38 PM] Sending request 'textDocument/codeAction - (69)'.
[Trace - 7:12:38 PM] Sending request 'textDocument/codeAction - (70)'.
[Trace - 7:12:38 PM] Sending notification 'textDocument/didChange'.
[Trace - 7:12:38 PM] Sending request 'textDocument/codeAction - (71)'.
[Trace - 7:12:38 PM] Sending request 'textDocument/codeAction - (72)'.
[Trace - 7:12:38 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 7:12:38 PM] Received response 'textDocument/codeAction - (66)' in 726ms.
[Trace - 7:12:38 PM] Sending request 'textDocument/codeAction - (73)'.
[Trace - 7:12:38 PM] Sending request 'textDocument/codeAction - (74)'.
[Trace - 7:12:38 PM] Sending notification 'textDocument/didChange'.
[Trace - 7:12:38 PM] Sending notification 'textDocument/didChange'.
[Trace - 7:12:38 PM] Sending request 'textDocument/codeAction - (75)'.
[Trace - 7:12:38 PM] Sending request 'textDocument/codeAction - (76)'.
[Trace - 7:12:39 PM] Sending notification 'textDocument/didChange'.
[Trace - 7:12:39 PM] Sending notification 'textDocument/didChange'.
[Trace - 7:12:39 PM] Sending request 'textDocument/codeAction - (77)'.
[Trace - 7:12:39 PM] Sending request 'textDocument/codeAction - (78)'.
[Trace - 7:12:39 PM] Sending notification 'textDocument/didChange'.
[Trace - 7:12:39 PM] Sending request 'textDocument/codeAction - (79)'.
[Trace - 7:12:39 PM] Sending request 'textDocument/codeAction - (80)'.
[Trace - 7:12:39 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 7:12:39 PM] Received response 'textDocument/codeAction - (67)' in 1121ms.
[Trace - 7:12:39 PM] Received response 'textDocument/codeAction - (68)' in 1120ms.
[Trace - 7:12:39 PM] Sending request 'textDocument/codeAction - (81)'.
[Trace - 7:12:39 PM] Sending request 'textDocument/codeAction - (82)'.
[Trace - 7:12:39 PM] Sending notification 'textDocument/didChange'.
[Trace - 7:12:39 PM] Sending request 'textDocument/codeAction - (83)'.
[Trace - 7:12:39 PM] Sending request 'textDocument/codeAction - (84)'.
[Trace - 7:12:39 PM] Sending notification 'textDocument/didChange'.
[Trace - 7:12:39 PM] Sending request 'textDocument/codeAction - (85)'.
[Trace - 7:12:39 PM] Sending request 'textDocument/codeAction - (86)'.
[Trace - 7:12:39 PM] Sending notification 'textDocument/didChange'.
[Trace - 7:12:39 PM] Sending request 'textDocument/codeAction - (87)'.
[Trace - 7:12:39 PM] Sending request 'textDocument/codeAction - (88)'.
[Trace - 7:12:39 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 7:12:39 PM] Received response 'textDocument/codeAction - (69)' in 1411ms.
[Trace - 7:12:39 PM] Received response 'textDocument/codeAction - (70)' in 1410ms.
[Trace - 7:12:40 PM] Sending notification 'textDocument/didChange'.
[Trace - 7:12:40 PM] Sending notification 'textDocument/didChange'.
[Trace - 7:12:40 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 7:12:40 PM] Received response 'textDocument/codeAction - (71)' in 1891ms.
[Trace - 7:12:40 PM] Received response 'textDocument/codeAction - (72)' in 1889ms.
[Trace - 7:12:40 PM] Received response 'textDocument/codeAction - (73)' in 1703ms.
[Trace - 7:12:40 PM] Received response 'textDocument/codeAction - (74)' in 1703ms.
[Trace - 7:12:40 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 7:12:41 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 7:12:41 PM] Received response 'textDocument/codeAction - (75)' in 2639ms.
[Trace - 7:12:41 PM] Received response 'textDocument/codeAction - (76)' in 2638ms.
[Trace - 7:12:41 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 7:12:42 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 7:12:42 PM] Received response 'textDocument/codeAction - (77)' in 3448ms.
[Trace - 7:12:42 PM] Received response 'textDocument/codeAction - (78)' in 3445ms.
[Trace - 7:12:42 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 7:12:42 PM] Received response 'textDocument/codeAction - (79)' in 3848ms.
[Trace - 7:12:42 PM] Received response 'textDocument/codeAction - (80)' in 3847ms.
[Trace - 7:12:42 PM] Received response 'textDocument/codeAction - (81)' in 3752ms.
[Trace - 7:12:42 PM] Received response 'textDocument/codeAction - (82)' in 3752ms.
[Trace - 7:12:43 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 7:12:43 PM] Received response 'textDocument/codeAction - (83)' in 4256ms.
[Trace - 7:12:43 PM] Received response 'textDocument/codeAction - (84)' in 4255ms.
[Trace - 7:12:43 PM] Received response 'textDocument/codeAction - (85)' in 4221ms.
[Trace - 7:12:43 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 7:12:43 PM] Received response 'textDocument/codeAction - (86)' in 4700ms.
[Trace - 7:12:44 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 7:12:44 PM] Received response 'textDocument/codeAction - (87)' in 5087ms.
[Trace - 7:12:44 PM] Received response 'textDocument/codeAction - (88)' in 5085ms.
[Trace - 7:12:44 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 7:12:45 PM] Received notification 'textDocument/publishDiagnostics'.

You can see the increasing delays towards the end.

I haven't yet tried the new version you posted a few days ago but I wanted to share this trace from a few mins ago. I'm currently working on a file that's 472 lines long.
I'm going to try your latest version now and I'll report back once I get a sense of if it's helping or not.
[Info  - 3:25:47 PM] ESLint server is running.
[Info  - 3:25:49 PM] ESLint library loaded from: /Users/mark/repos/scout-client/node_modules/eslint/lib/api.js
[Trace - 4:56:21 PM] Sending notification '$/setTraceNotification'.
[Trace - 4:56:21 PM] Sending notification 'workspace/didChangeConfiguration'.
[Trace - 4:56:22 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 4:56:23 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 4:56:23 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 4:56:23 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 4:56:23 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 4:56:23 PM] Received notification 'eslint/status'.
[Trace - 4:56:24 PM] Sending request 'textDocument/codeAction - (1268)'.
[Trace - 4:56:24 PM] Received response 'textDocument/codeAction - (1268)' in 27ms.
[Trace - 4:56:27 PM] Sending notification 'textDocument/didChange'.
[Trace - 4:56:27 PM] Sending notification 'textDocument/didChange'.
[Trace - 4:56:27 PM] Sending request 'textDocument/codeAction - (1269)'.
[Trace - 4:56:28 PM] Sending notification 'textDocument/didChange'.
[Trace - 4:56:28 PM] Sending request 'textDocument/codeAction - (1270)'.
[Trace - 4:56:28 PM] Sending notification 'textDocument/didChange'.
[Trace - 4:56:28 PM] Sending request 'textDocument/codeAction - (1271)'.
[Trace - 4:56:28 PM] Sending notification 'textDocument/didChange'.
[Trace - 4:56:28 PM] Sending request 'textDocument/codeAction - (1272)'.
[Trace - 4:56:28 PM] Sending notification 'textDocument/didChange'.
[Trace - 4:56:28 PM] Sending request 'textDocument/codeAction - (1273)'.
[Trace - 4:56:28 PM] Sending notification 'textDocument/didChange'.
[Trace - 4:56:28 PM] Sending request 'textDocument/codeAction - (1274)'.
[Trace - 4:56:28 PM] Sending notification 'textDocument/didChange'.
[Trace - 4:56:28 PM] Sending request 'textDocument/codeAction - (1275)'.
[Trace - 4:56:28 PM] Sending notification 'textDocument/didChange'.
[Trace - 4:56:28 PM] Sending request 'textDocument/codeAction - (1276)'.
[Trace - 4:56:29 PM] Sending notification 'textDocument/didChange'.
[Trace - 4:56:29 PM] Sending request 'textDocument/codeAction - (1277)'.
[Trace - 4:56:29 PM] Sending notification 'textDocument/didChange'.
[Trace - 4:56:29 PM] Sending request 'textDocument/codeAction - (1278)'.
[Trace - 4:56:29 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 4:56:29 PM] Received notification 'eslint/status'.
[Trace - 4:56:29 PM] Received response 'textDocument/codeAction - (1269)' in 1370ms.
[Trace - 4:56:29 PM] Sending notification 'textDocument/didChange'.
[Trace - 4:56:30 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 4:56:30 PM] Received notification 'eslint/status'.
[Trace - 4:56:30 PM] Sending notification 'textDocument/didChange'.
[Trace - 4:56:30 PM] Sending request 'textDocument/codeAction - (1279)'.
[Trace - 4:56:30 PM] Sending notification 'textDocument/didChange'.
[Trace - 4:56:30 PM] Sending request 'textDocument/codeAction - (1280)'.
[Trace - 4:56:31 PM] Sending notification 'textDocument/didChange'.
[Trace - 4:56:31 PM] Sending request 'textDocument/codeAction - (1281)'.
[Trace - 4:56:31 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 4:56:31 PM] Received notification 'eslint/status'.
[Trace - 4:56:31 PM] Received response 'textDocument/codeAction - (1270)' in 3813ms.
[Trace - 4:56:32 PM] Sending notification 'textDocument/didChange'.
[Trace - 4:56:32 PM] Sending request 'textDocument/codeAction - (1282)'.
[Trace - 4:56:32 PM] Sending notification 'textDocument/didChange'.
[Trace - 4:56:32 PM] Sending request 'textDocument/codeAction - (1283)'.
[Trace - 4:56:32 PM] Sending notification 'textDocument/didChange'.
[Trace - 4:56:32 PM] Sending request 'textDocument/codeAction - (1284)'.
[Trace - 4:56:33 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 4:56:33 PM] Received notification 'eslint/status'.
[Trace - 4:56:33 PM] Received response 'textDocument/codeAction - (1271)' in 4893ms.
[Trace - 4:56:33 PM] Sending request 'textDocument/codeAction - (1285)'.
[Trace - 4:56:33 PM] Sending notification 'textDocument/didChange'.
[Trace - 4:56:33 PM] Sending request 'textDocument/codeAction - (1286)'.
[Trace - 4:56:33 PM] Sending notification 'textDocument/didChange'.
[Trace - 4:56:33 PM] Sending request 'textDocument/codeAction - (1287)'.
[Trace - 4:56:33 PM] Sending notification 'textDocument/didChange'.
[Trace - 4:56:33 PM] Sending request 'textDocument/codeAction - (1288)'.
[Trace - 4:56:33 PM] Sending notification 'textDocument/didChange'.
[Trace - 4:56:33 PM] Sending request 'textDocument/codeAction - (1289)'.
[Trace - 4:56:33 PM] Sending notification 'textDocument/didChange'.
[Trace - 4:56:33 PM] Sending request 'textDocument/codeAction - (1290)'.
[Trace - 4:56:34 PM] Sending notification 'textDocument/didChange'.
[Trace - 4:56:34 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 4:56:34 PM] Received notification 'eslint/status'.
[Trace - 4:56:34 PM] Received response 'textDocument/codeAction - (1272)' in 6233ms.
[Trace - 4:56:35 PM] Sending notification 'textDocument/didChange'.
[Trace - 4:56:35 PM] Sending notification 'textDocument/didSave'.
[Trace - 4:56:35 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 4:56:35 PM] Received notification 'eslint/status'.
[Trace - 4:56:35 PM] Received response 'textDocument/codeAction - (1273)' in 7342ms.
[Trace - 4:56:35 PM] Received response 'textDocument/codeAction - (1274)' in 7177ms.
[Trace - 4:56:37 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 4:56:37 PM] Received notification 'eslint/status'.
[Trace - 4:56:38 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 4:56:38 PM] Received notification 'eslint/status'.
[Trace - 4:56:38 PM] Received response 'textDocument/codeAction - (1275)' in 9908ms.
[Trace - 4:56:39 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 4:56:39 PM] Received notification 'eslint/status'.
[Trace - 4:56:39 PM] Received response 'textDocument/codeAction - (1276)' in 11039ms.
[Trace - 4:56:39 PM] Received response 'textDocument/codeAction - (1277)' in 10899ms.
[Trace - 4:56:41 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 4:56:41 PM] Received notification 'eslint/status'.
[Trace - 4:56:41 PM] Received response 'textDocument/codeAction - (1278)' in 12266ms.
[Trace - 4:56:42 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 4:56:42 PM] Received notification 'eslint/status'.
[Trace - 4:56:44 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 4:56:44 PM] Received notification 'eslint/status'.
[Trace - 4:56:47 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 4:56:47 PM] Received notification 'eslint/status'.
[Trace - 4:56:47 PM] Received response 'textDocument/codeAction - (1279)' in 16471ms.
[Trace - 4:56:47 PM] Received response 'textDocument/codeAction - (1280)' in 16393ms.
[Trace - 4:56:50 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 4:56:50 PM] Received notification 'eslint/status'.
[Trace - 4:56:50 PM] Received response 'textDocument/codeAction - (1281)' in 19501ms.
[Trace - 4:56:52 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 4:56:52 PM] Received notification 'eslint/status'.
[Trace - 4:56:53 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 4:56:53 PM] Received notification 'eslint/status'.
[Trace - 4:56:53 PM] Received response 'textDocument/codeAction - (1282)' in 21026ms.
[Trace - 4:56:54 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 4:56:54 PM] Received notification 'eslint/status'.
[Trace - 4:56:54 PM] Received response 'textDocument/codeAction - (1283)' in 22170ms.
[Trace - 4:56:54 PM] Received response 'textDocument/codeAction - (1284)' in 22122ms.
[Trace - 4:56:54 PM] Received response 'textDocument/codeAction - (1285)' in 21816ms.
[Trace - 4:56:56 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 4:56:56 PM] Received notification 'eslint/status'.
[Trace - 4:56:57 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 4:56:57 PM] Received notification 'eslint/status'.
[Trace - 4:56:57 PM] Received response 'textDocument/codeAction - (1286)' in 24126ms.
[Trace - 4:56:58 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 4:56:58 PM] Received notification 'eslint/status'.
[Trace - 4:56:58 PM] Received response 'textDocument/codeAction - (1287)' in 25030ms.
[Trace - 4:56:59 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 4:56:59 PM] Received notification 'eslint/status'.
[Trace - 4:56:59 PM] Received response 'textDocument/codeAction - (1288)' in 25827ms.
[Trace - 4:57:00 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 4:57:00 PM] Received notification 'eslint/status'.
[Trace - 4:57:00 PM] Received response 'textDocument/codeAction - (1289)' in 26683ms.
[Trace - 4:57:01 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 4:57:01 PM] Received notification 'eslint/status'.
[Trace - 4:57:01 PM] Received response 'textDocument/codeAction - (1290)' in 27543ms.
[Trace - 4:57:02 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 4:57:02 PM] Received notification 'eslint/status'.
[Trace - 4:57:03 PM] Received notification 'textDocument/publishDiagnostics'.
[Trace - 4:57:03 PM] Received notification 'eslint/status'.

@Kovensky @mwadden thanks a lot for the traces. I know better understand what is going on. I will look into a new version of the extension for you. From my first analysis this will requires some changes in the VS Code core as well since we are triggering far too many codeAction requests.

We fixed parts of this in master which is already in insider (thanks to @jrieken). However there is more work to do which has to happen in the ESLint extension. The problem is that codeAction requests should only be sent if the diagnostic the code action is requested for contains a ESLint generated error. Otherwise ESLint is not able to provide any code action.

@Kovensky @mwadden @benduran @dlong500
Attached a new version of the eslint extension. Please follow the steps in https://github.com/Microsoft/vscode-eslint/issues/215#issuecomment-291454472 to install.
The extension requires features from the insider build to work optimal. It is working with stable as well but it will not profit so much.
Please let me know if this improves your experience (note that I am out on vacation next week so it will take a little for me to respond).
vscode-eslint-1.2.9.zip

Running code --install-extension vscode-eslint-1.2.9.vsix with the new extension is failing with:
[ { Error: ENOENT: no such file or directory, open '~/.vscode-insiders/extensions/dbaeumer.vscode-eslint-1.2.9/package.json'
    errno: -2,
    code: 'ENOENT',
    syscall: 'open',
    path: '~/.vscode-insiders/extensions/dbaeumer.vscode-eslint-1.2.9/package.json' } ]

@Kovensky sorry for that. Since I didn't official publish I didn't increment the version number.

Wanted to mention that the latest version you've provided has improved the performance again, but there is still some "catching-up" that eslint is doing when my settings are set to run onType. I will work on getting a trace for you within the next few days.

@benduran thanks. Would you be able to share your workspace. Would ease tracking this down further.

Quick update... I've been using the version from Apr 4th for a few weeks now and it's been great. No noticeable concerns. I just installed the latest version from Apr 13th now so I'll give a few days and report back.
Thx again for the quick turnaround on fixing this, it's made vscode usable again!

Following up from my last comment, it's been a few days now of heavy usage and everything seems great still.

Great to hear.

I have everything up to date, including the ESLint plugin with latest version and this is still happening.
For me this started appearing after updating Watchman to the latest version.

@ItsNoHax can you please open a new issue with steps to reproduce (best would be a clonable GitHub repository).

Not sure I can, this is happening at my work's React-Native project which has a substantial size code base which could be related to why it's sluggish.

@ItsNoHax something like this is hard to track down without a test case :-(

source: gharchive/issue

authors: ItsNoHax Kovensky benduran dbaeumer dlong500 mwadden

repo: Microsoft/vscode-eslint

license: MIT

license_type: permissive

license_source: github-api


text:
ignoreEOLComments has additional properties

From @xovel on September 17, 2017 16:35

VSCode Version: Code 1.16.1 (27492b6bf3acb0775d82d2f87b25a93490673c6d, 2017-09-14T16:38:23.027Z)
OS Version: Windows_NT x64 10.0.15063
Extensions:

Extension
Author (truncated)
Version

vscode-color
ans
0.4.5

vscode-eslint
dba
1.3.1

githistory
don
0.2.3

beautify
Hoo
1.1.1

vscode-regexp-preivew
le0
0.0.3

sublime-keybindings
ms-
2.9.1

debugger-for-chrome
msj
3.3.0

material-icon-theme
PKi
2.2.1

java
red
0.10.0

Steps to Reproduce:

Open a front-end project
Warning come...

Warning text:

e:\svn\drs-frontend.eslintrc.yml: Configuration for rule "no-multi-spaces" is invalid: Value "data["0"].ignoreEOLComments" has additional properties.

Reproduces without extensions: Yes

My .eslintrc.yml:
...
  no-magic-numbers: 0

  # 禁止多个空格
  # no-multi-spaces: 0
  no-multi-spaces:
    - 2
    -
      ignoreEOLComments: true
      exceptions:
        Property: true
        VariableDeclarator: true
        ImportDeclaration: true

  # 禁止多行字符串
  no-multi-str: 1

...

Copied from original issue: Microsoft/vscode#34544

@xovel do you see the same error when executing ESLint from a terminal ?

@dbaeumer No, eslint works very well while using a bash CLI.
I try to reinstall eslint, but failed again.

@xovel can you provide me with a GitHub repository I can clone to reproduce this?

I cannot reproduce this quirk problem again.
BUT, I just solved it by reinstalling eslint, the warning is not shown again.
I think this maybe caused by the old version eslint. The version of eslint in our project before update is v3.0.1, but ignoreEOLComments is supported in v4.0.0.

@xovel thanks for the clarification. Closing the issue then.

authors: dbaeumer xovel


text:
es warning

how to remove es6  warning

I think this is better ask in the ESLint channel (stack overflow) since this is a contfiguration of ESLint npm itself. The VS Code extension is based on ESLint npm. A good way to tweak things like this is to execute eslint in a terminal to see how standard eslint behaves.

authors: dbaeumer soydepr


text:
Add support to some how attach a debug session to a remote instance of python process

E.g. attach debugger to remote docker container

That would be great. This is something, that I miss most when working in with docker-compose in my workflow. If there is a way to enable this working with docker quickly that would be super awesome!

This is possible today, this is achieved via Remote Debugging feature.

Option 1: Please have a look at the Remote debugging section in the documentation.
Option 2: You can use the experimental debugger to achieve this as follows:

pip install ptvsd --pre into your docker container
Start the program in debug mode (use the following as the value for CMD in your docker file: python -m ptvsd --server --port 5678 --file xyz.py
Where 5678 is the port to be exposed for debugging, and xyz.py is the file to be debugged.
Note: You'll need to use the experimental debugger.

E.g. attach debugger to remote docker container

Unfortunately there's no way to attach to a remove process. The only way to achieve something similar is:

Launch the remote process (docker container) and host the debugger libraries
Please see the two solutions provided in the previous section.

@brettcannon Not sure why we're flagging this as an enhancement?

@brettcannon When I created this issue, I don't quite remember the use case for this. Currently we can do this with the remote debugging options we have.
Once the experimental debugger is released, I believe we can close this issue.

I think you opened this to provide some UX for it to occur so it wasn't so manual.

This issue is outdated, we're looking at other ways of solving this

authors: DonJayamanne brettcannon galuszkak qubitron

repo: Microsoft/vscode-python


text:
Provide npm package with CLI

If you look at the example of markdownlint, I'm not only able to globally and locally suppress checks, I can use an npm package for the code and a cli npm pacakge to add the linting to my build process.
This should be added for cSpell. For better form the .vscode/cSpell.json file should probably be put in the root as a .cspellrc.json file.
If interested, I would also recommend that a cspell npm package (and yes it is available) should include the CLI.

Sorry, wrong repo. Looking for vscode-spell-checker.

repo: Microsoft/vscode-spell-check

license: mit

license_source: bigquery


text:
Autocomplete should insert parenthesis for methods

During autocompletion for methods, parenthesis do not get inserted automatically. Most of the time they are required and it's easier to delete them than insert them manually.
Eg: Tab or Return after var arr = str.sp should autocomplete to var arr = str.splice() rather than var arr = str.splice with the cursor between the parenthesis.

Not sure I agree with this as the default behavior, in JS and more functional languages in particular it is quite common to use functions as references such as passing them in as arguments. Something like this could irritate developers when they're used to typing () anyhow. An example of where this would get annoying:
var func = function (a, b) { /*...*/ }
if (func) {
  someFunction(func);
  someOtherFunction(func.bind(null, x, y));
}

Do you know any editors/IDEs that use this as the default?

Calling methods is common than passing them as arguments. Many IDEs like WebStorm, IntelliJ Idea and Android Studio use this as default behaviour and it really helps in coding faster.
I understand that this could irritate developers who are accustomed to typing parenthesis but for other developers who come from the JetBrains world, it becomes an extra effort. A simple option to enable this behaviour in settings would really help. :+1:

After using Cloud9 IDE online and then switching to Visual Studio Code for offline work makes you realise the importance of the feature. Will it be available in the future?

Totally agree on @xeoneux :+1: . If one just wants the identifier, it is just one backspace away. I have been quite annoyed by this also. It seems like the autocomplete suggests me a variable and not a function or method.

We have experimented with different options in the past. Currently we defer it to the language service.
CC @jrieken.

for TypeScript this should still be supported with the useCodeSnippetsOnMethodSuggest setting

useCodeSnippetsOnMethodSuggest option for JS and TS works beautifully! I wonder why it isn't enabled by default. Thanks @jrieken

For C# there is open issue for now https://github.com/dotnet/roslyn/issues/12363

authors: Tyriar egamma jrieken neooleg tinganho xeoneux

repo: Microsoft/vscode


text:
Perf: renderer blocks when doing gulp watch and having many files open

Steps to Reproduce:

have many files open (50+)
run gulp watch

=> close to the end when files are being written, the UI hangs
=> seems to be a large amount of deletes hitting our checks for disposing editor models if the associated file gets deleted
/cc @joaomoreno

@joaomoreno can you please attach a profile from dev tools when this happens? I just tried to reproduce with 200 open TS files and could not see this slowdown :-/

Can't repro at home either. Let's do it in the office.

We can still see to plan this for September if it turns out to be a low risk fix.

I can reproduce in selfhost now. The critical path is FileEditorInput.onFileChanges which gets called a lot during gulp watch. Having a lot of FileEditorInputs around does not help either.

Related to https://github.com/Microsoft/vscode/issues/13283

Actually marking as duplicate.

authors: bpasero joaomoreno


text:
Code snippets and other suggestions stop working

VSCode Version: 1.7.1
OS Version: Windows 10

Sometimes on creating a new file, code snippets, and other suggestions refuse to work.
Steps to Reproduce:

Create new file within VSCode
Try to use code snippet, or anything to get suggestions up

@BlueOrange775 can you provide a project or file that you are working which reproduces this problem?

could be related to https://github.com/Microsoft/vscode/issues/15105

Issue is related to an extension, which has been fixed.

authors: BlueOrange775 rebornix wUFr


text:
Feature request: Show hidden characters like: space, tab, end of line, carriage return

VSCode Version:1.8
OS Version: Windows 10, Linux, Mac

Steps to Reproduce:
Hello VSCode Team,
Please create a new feature in view optin to show hidden characters like: space, tab, end of line(LF), carriage return (CR).
This basic option is available in Atom and Notepad++ which makes a script editor powerful.
Right now this option is not available in vscode 1.8.
Thanks,
Regards,
Gabor

@citygabor
You can use editor.renderWhitespace: "all" to get spaces and tabs rendered and you can see the line ending of the file in the bottom right corner (LF or CRLF)

@alexandrudima,
Finally I also found View -> Ctrl+Shift+i does the same which is Toggle Render Whitespace.
Please provide the information how to make different tab or dots. I can see only dots even I press tab.
I attached the screen which should be look like arrow for tab and dot for space.

Platform: Windows 10
Version: 1.8, 1.9
Thanks,
regards,
Gabor

@citygabor Please ask such questions on stack overflow -  http://stackoverflow.com/questions/tagged/vscode

@alexandrudima I still want to see end-of-line characters in-file, because I can have files with literal strings that have carriage returns and linefeeds everywhere else. Is it possible to turn this on?

authors: alexandrudima citygabor masaeedu


text:
Code crashes / slows down after a period of time

After using VS Code for a while, it gets slower and slower. I notice it particularly when it attempts to auto-complete.
It will then sometimes crash. It may crash whilst I'm using it. It may crash when I haven't used it for sometime but using another window. It may crash if I leave the PC overnight. It may crash if I only used it for a very short amount of time and the slowdown above hadn't occurred.
Looking at the Windows Task Manager does not show it using any more memory at this time (it peaks at around 38MB and never goes above 1% CPU although is usually at 0%). The PC has plenty of resources/memory free.
Unfortunately I can't find a pattern. It is worse now though than it was when it first started occurring several releases ago.
I just get a dialog "Visual Studio has crashed. We are sorry for the inconvenience! Please restart Visual Studio Code." and no other indication as to the cause.
Code v0.10.6, issue has occurred since around v0.3
Windows 8.1, i7-4770 with 16GB RAM. SSD disk.
Git repository contains over 39,000 files across folders at various levels deep. These are mostly HP BASIC .BAS (OpenVMS files which we maintain on Windows) plus bespoke 4GL files.
I don't use any of the git functionality within Code, I do commits etc externally.
I use Ctrl+E frequently to find/open files.
Shift+Ctrl+B runs a windows .bat file to transfer and compile the code
settings.json:  "editor.insertSpaces": true, "files.trimTrailingWhitespace": true

Probably a duplicate of https://github.com/Microsoft/vscode/issues/508

Looking at the Windows Task Manager does not show it using any more memory at this time (it peaks at around 38MB

Add the "Commit Size" column and check that. The default memory column is only private working set.

Yeah, #508

I see this is now marked as a duplicate, but just to follow up from @Elusive138, I've now added the commit size to the task manager and I see it does increase over time (regardless of whether I'm using Code or not).
It's currently at 300MB and rising. Code has only had a little use this morning.

authors: Elusive138 Tyriar bpasero gushie


text:
JSDoc IntelliSense for anonymous functions doesn't include parameters

Testing #21031

Looking through the TypeScript implementation, it looks like this is by design currently but I agree that we should have consistent behavior for function expressions as well

Tracked upstream by https://github.com/Microsoft/TypeScript/issues/14280

authors: mjbvz mousetraps


text:
Cancelling the file creation by scrolling causes the Explorer shows not correctly

VSCode Version: Code 1.10.2 (8076a19fdcab7e1fc1707952d652f0bb6c6db331, 2017-03-08T14:02:52.799Z)
OS Version: Windows_NT ia32 10.0.14393

Steps to Reproduce:

open a folder such as "vscode-master"
expand folder "build" then "monaco"
click the "New File" button, then scroll to cancel the file creation
do step 3 again (sometimes not needed)
collapse and expand "monaco" for several times, the Explorer shows not correctly

When the Explorer shows not correctly, scrolling makes it even worse..
And when something like this happens, we have to reopen VSCode to make it normal.

Can you try to reproduce with our nightly insider builds? You can give our preview releases a try from: http://code.visualstudio.com/Download#insiders

Seems to still have problem, here is a screenshot of video 0:0:39

VSCodeExplorer.zip

@King66 thanks, I can reproduce!
@joaomoreno looks like another tree bug to me similar to the one we fixed last week!

Awesome steps!

Closing and opening the Explorer pan will reset it and resolve the problem without having to restart VSCode.

Actually closing and reopening the Explorer view just changes the issue. The scrolling problem stops but now I have files disappearing and being out of order.

By the way, this bug still exists, more than one year after this issue was created.
I'm on this version/system:
Version 1.23.0-insider
Commit ab56a0952b9c2ff7add6404f80ebf9398cf8ae51
Date 2018-04-17T05:16:42.105Z
Shell 2.0.0-beta.7
Renderer 61.0.3163.100
Node 8.9.3
Architecture x64

Screencast: http://recordit.co/21kC41SMaB

Relates to #68821
The behavior is changed in release 1.31, scrolling no longer cancels file creation, but the content of input box is lost when scrolling.

This appears fixed.

authors: CherryDT King66 bpasero joaomoreno justincy yume-chan


text:
getWordAtPosition is slow in very long lines

large_files\result - Copy.js
go to last line
click around

CPU-20160126T123125.cpuprofile.txt

The problem seems to stem from this function:
https://github.com/Microsoft/vscode/blob/master/src/vs/editor/common/modes/snippetsRegistry.ts#L108
For some reason it looks like it is being compiled to code that parses the entire line, instead of just the 100 character cap. The translated of said function javascript:
export function getNonWhitespacePrefix(model: IReadOnlyModel, position: IPosition) : string { 	let line = model.getLineContent(position.lineNumber).substr(0, position.column - 1); 	let match = line.match(/[^\s]+$/); 	if (match) { 		return match[0]; 	} 	return ''; }
Worth looking into, making that function do nothing as a quick check seems to solve the problem.

Sweet!

authors: alexandrudima marktrz


text:
Salsa does not honour JSDoc on prototype assignments

Testing #2218
function Person() {
    this.name = 'John';
}

/**
 * @param {string} to
 */
Person.prototype.sayHi = function(to) {
    console.log('Hi ' + to + ', I\'m ' + this.name);
}

/**
 * @param {string} to
 */
function sayHi(to) {

}

This is tracked by https://github.com/Microsoft/TypeScript/issues/6552

closing

authors: alexandrudima billti egamma


text:
New log files are created after changing the log settings

Testing #25334
Steps to Reproduce:

Change the typescript.tsserver.log setting to verbose
Open the logs
Stop the logging Off
Restart ts server
Change again to verbose
Open the log

You see a new log file.
Why is it not shown in the same log file?

This is as designed. Every ts-server instance is supposed to have its own log file


text:
JSON schema validation should support defining the problem severity

Currently all schema problems are flagged as warnings. Would be cool if I can control this and sometimes make them errors.

@dbaeumer Can you give an example on which validation issues would be an error and which ones a warning?

For example if I define additionalProperties: false and someone adds a not defined property I would expect an error. Showing this as a warning is IMO confusing since for example deprecations are shown as a warning as well.

authors: aeschli dbaeumer


text:
Can no longer open image files from the git viewlet

Add a .png file to a git repo (or rename an existing one so it shows up in the Git viewlet)
See the untracked PNG in the git viewlet
Click on it

See Git: cannot open file:///Users/roblou/code/vscode/resources/linux/code2.png. Detail: File seems to be binary and cannot be opened as text
Previously, it would open the image.

#3935

This is a regression when the file is untracked and thus new should open like a normal file.

Thanks. I thought it had worked recently.

Dupe of #33850

authors: bpasero joaomoreno roblourens


text:
有没有快速切换文件后缀的快捷键，就算右下角的文件后缀。比如js后缀快速切换成html后缀

VSCode Version:
OS Version:

Steps to Reproduce:
1.有没有快速切换文件后缀的快捷键，就算右下角的文件后缀。比如js后缀快速切换成html后缀
2.有没有快速切换文件后缀的快捷键，就算右下角的文件后缀。比如js后缀快速切换成html后缀

Reproduces without extensions: Yes/No

Translatation: There is no quick to change the file suffix shortcut keys, even if the lower right corner of the file suffix. Such as js suffix quickly switch to html
There is a key binding for the Change Language Mode command: CTRL+K M

authors: egamma leeseean


text:
launch.json for new java debug extension

Hi! humans. I'm having trouble figuring out this launch.json stuff. I'm supposed to enter the fully qualified name of the mainClass but i have no idea what that is. I've tried a bunch of things but i can't figure it out.
i keep getting this error:
Failed to resolve classpath: Main class 'com.java.first' doesn't exist in the workspace.
PLEASE HELP!!
here's the launch.json settings
{
// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
"version": "0.2.0",
"configurations": [
{
"type": "java",
"name": "Debug (Launch)",
"request": "launch",
"mainClass": "com.java.first", //here's where i'm having an issue. i don't know anything about this.
"args": ""
},
{
"type": "java",
"name": "Debug (Attach)",
"request": "attach",
"hostName": "localhost",
"port": 0
}
]
}

VSCode Version: Code 1.17.1 (1e9d36539b0ae51ac09b9d4673ebea4e447e5353, 2017-10-10T14:24:50.851Z)
OS Version: Windows_NT x64 10.0.15063
Extensions:

Extension
Author (truncated)
Version

php-debug
fel
1.11.1

cpptools
ms-
0.13.1

debugger-for-chrome
msj
3.3.1

java
red
0.11.0

vscode-icons
rob
7.15.0

vscode-java-debug
vsc
0.1.0

vscode-java-pack
vsc
0.1.0

Steps to Reproduce:

Reproduces without extensions: Yes/No

Please file this against the java extension you are using. Thank you

authors: hajiskyy isidorn


text:
Auto Import for JavaScript and TypeScript

VSCode Version: 1.19.0-insider (1.19.0-insider)
OS Version: macOS Sierra 10.12.6 (16G1036)

I use TSLint. I added ordered imports in my rules. Maybe imports auto alphabetized.

This falls under https://github.com/Microsoft/TypeScript/issues/10020

authors: mjbvz sqlProvider


text:
The automatic build with webpack doesn't work where the project is in the workspace!

VSCode Version:1.18.1
OS Version:Ubuntu  16.04 lts

Steps to Reproduce:
1.When I run code in the nodejs + webpack + react + vscodeworkspace . I typed the npm run dev start nodejs server with  webpack plugin ''webpack-hot-middleware'' that can detect the file changes and automatically  build project .  But it seems that it doesn't work at all when I changed files and save. And when I process the project by a singe project rather than in a workspaces, It works well. SO.. I don't know whether this is a bug or not, and give this issue..
2.

Reproduces without extensions: Yes/No

It's very hard to understand. What is the specific issue with VS Code that you are facing?

@joaomoreno
I'm so sorry to my poor English !
I mean that when I run the  react code with the VSCDOE's new feature Multi-root workspaces.
The express plugin "webpack-hot-middleware" which can detect the changes on the files and auto publish  doesn't work. But when I run code without Multi-root workspaces, the plugin works well...

This sounds to me like an issue with webpack not VS Code. Closing.

authors: bpasero joaomoreno wangyi7099


text:
New terminal created for task isn't activated

I have a build task that has "presentation.panel" = "new"
When I build, it creates a new terminal for the task's output; but it does not activate it (so you have to manually select it in the drop-down list)
Also, the terminal that it does create seems to be very narrow (wrapping all the text)
This is a regression from version 1.21

@elpixo this works for me using 1.22.
Which OS are you on ?

Linux.

More info; it seems that switching "reveal" to "always" makes the panel pop up.
So perhaps the error lies with the problem matcher.
Here's the first part of my tasks.json - the script calls clang++ to compile.
 "tasks": [
      {
         "label": "Build",
         "type": "shell",
         "group": {
            "kind": "build",
            "isDefault": true
         },
         "command": "${workspaceRoot}/build.sh",
         "presentation": {
            "reveal": "silent",
            "panel": "new"
         },
         "problemMatcher": {
            "owner": "Build",
            "fileLocation": [
               "absolute"
            ],
            "pattern": {
               "regexp": "^([^:]+):(\\d+):(\\d+):\\s+(warning|error):\\s+(.*)$",
               "file": 1,
               "line": 2,
               "column": 3,
               "severity": 4,
               "message": 5
            }
         }
      },

Just to be clear; I'm expecting it to pop up when there is a problem (I can confirm that even when there is a problem shown in the "problems" view - the terminal does not pop up)

@elpixo now I see. And I agree that 'silent' should make it pop up when an error occurs.

I can't find the duplicate, but silent now does this.

authors: alexr00 dbaeumer elpixo


text:
[loc][Query] Context needed for "contribution point"

For string below community members are asking about more context? Can you please help? Thanks!
Original comments
BG ISSUE - This is unclear. And what do the 'contribution point' and 'conributed' mean here?
by lyubomirv, 6 hours ago
ES - @johosek , can you help me to understand on what means "contribution point" in the file source in https://github.com/Microsoft/vscode/raw/master/src/vs/workbench/api/browser/viewsContainersExtensionPoint.ts line: 44
Thanks.
by AleksSyntek, 11 hours ago
Context
src/vs/workbench/api/browser/viewsContainersExtensionPoint:English (en):plaintext:vscode.extension.contributes.views.containers.id
Resource
vs_workbench
String Hash
bb64f8d530c8baeb8d85950114a52101
String text
Unique id used to identify the container in which views can be contributed using 'views' contribution point

Same concern about "contribution" applies to next string from the same file.
String - '{0}' contribution is only available when running out of dev or with the following command line switch: --enable-proposed-api {1}
Comment - What is 'contribution' here? by lyubomirv, 6 hours ago

Contribution refers to those that an extension contributes to VS Code.

@sandy081 I'm sorry but it's not clear. I still do not understand what is a 'contribution POINT'?
And for the other concern - '{0}' contribution. What does this mean? What could {0} be replaced with?

@lyubomirv Contribution point is an extension point in package.json to which extensions contribute to. For eg:
"contributes": {
	"viewsContainers": {
		"activitybar": [
                        {
			    "id": "azure",
			    "title": "Azure",
			     "icon": "resources/azure.png"
		        }
                  ]
	},
        "views": {
		"azure": [
			{
				"id": "cosmosdb",
				"name": "Azure Cosmos DB"
			},
                         {
				"id": "docker",
				"name": "Docker"
			}
		]
	}
}

In the above example viewsContainers and views are contribution points.
I just updated the message to replace {0} directly with viewsContainers because it should not be translated.

Thanks @sandy081 for the explanation on that. I will recheck the translation item.

@sandy081 Thank you!

authors: AleksSyntek josefhosek lyubomirv sandy081


text:
1.25 thrashing and then crashing under Windows 10

I was not able to find anyone else reporting similar problems but I had to revert to 1.24.1 after repeated experiments with 1.25. I don't have a trace or much of use but I will describe my experience and hope that additional information can be added by others if I'm not the only one who experienced this.
Last night I did the update and read through the release notes excited by the new windowing layout and other features. From the outset, however, performance was laggy and I suspected the animated images in the release notes, but the problem persisted.
I saw a thin progress bars in the top area of the editor panel on occasion and wondered if, like Eclipse, the language services were trying to slurp up relevant data in some of the larger projects but even smaller projects appeared to have the same problem. The interface becomes unresponsive, taking the CPU to the point of not allowing the mouse to move.
Typically, this would eventually lead to a dialog about restarting without much additional information other than reporting a crash.
I started the process of narrowing things down.

Uninstalled, reinstalled.
Renamed user folder (removing all custom configuration and extensions).
Tried to find root causes, repeatable actions, doesn't seem tied to specific activities.

I cannot afford to spend more time on this at the moment but uninstalling and installing 1.24.1 works fine. I even repeated this, uninstalling 1.24.1 and installing 1.25 again, to no avail. I have removed it and am currently working with 1.24.1 to stay productive.
Any advice on find the root cause would be useful. I will try to find time this weekend to try anything that makes sense. If anyone else is having similar issues, I presume they can be added to this ticket if the symptoms are the same.

VSCode Version:
1.25.0
OS Version:
Windows 10

Steps to Reproduce:

Install 1.25.0 on Windows 10
Open projects and do normal actions like loading a file into the editor or navigating the file system or menus.

Does this issue occur when all extensions are disabled?: YES

When this happens - can you follow this guide: https://github.com/Microsoft/vscode/wiki/Performance-Issues#visual-studio-code-is-consuming-a-lot-of-cpu. Also, does this happen when justing open files or when reading release note.

I was able to resolve this using the prescribed tooling and disabling extensions that appeared to operate poorly. thanks for the assistance.

@claudeduguay I'm facing the exact same issue and disabling all extensions worked. I'm now trying to selectively enable some extensions to find the culprit. Which extension was the culprit in your case?

authors: an5rag claudeduguay jrieken


text:
Problems: light bulb and error should be two icons

Refs: #54861
The current light bulb next to the red error is practicaly invisible.
I suggest to increase the size of the light bulb such that it can actualy be seen.
I like that the red error is the main thing in this icon, but the light bulb should be more distunigishable, either by size or by some border lines or contrast.
An alternative is to render two icons next to one another.

Actually I like rendering two icons because then we could also trigger context menu on light bulb icon click - would be consistent with editor light bulb experience and would be more discoverable.

@isidorn I am discussing this with @misolori and we agreed upon showing two icons. Light bulb icon will be shown at the end just like an action.

That makes sense. The only downside of that is that the lightbulb will be disconnected due to the large horizontal size of the problem panel.
However I prefer that to the current solution.

Yeah position is far away, I can also try placing it at the very end of the message.

Experiment with both and whatever seems better for you works for me.
I would also consider putting it next to the error icon.

Putting it next to the error icon might need to accommodate some space for it. If an entry does not have quick fixes then it will be empty if not, it will be misaligned.

I would expect that space to be empty if entry does not have quick fixes. Would have to see it to decide if this is any good.
Though leaving up to you to decide

Check out this

Much better. I guess it also shows on mouse hover.

Yes


text:
source control branch workspace

A great feature would be if every source control branch would have its own workspace/state - meaning, once the user switch branch it will open all the files that were opened when the user last worked on this branch.

Duplicate Preserve open files list when switching branches (#35307)


text:
html word wrap not work

Issue Type: Bug
Even set 'Editor: Word Wrap' to 'wordWrapColumn' or 'bounded', and set 'Editor: Word Wrap Column' to '120' or other number value, the html code has already passed 120 words in one line, but the editor's wordWrap also can't work.
This's not conveniently for user to see and write the html code in the editor.
I hope the editor's developer can fixed this bug very soon.

VS Code version: Code 1.27.2 (f46c4c469d6e6d8c46f268d1553c5dc4b475840f, 2018-09-12T16:17:45.060Z)
OS version: Windows_NT x64 6.1.7601

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-4460  CPU @ 3.20GHz (4 x 3192)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
7.95GB (0.90GB free)

Process Argv
D:\Program Files\Microsoft VS Code\Code.exe

Screen Reader
no

VM
0%

Extensions (40)

Extension
Author (truncated)
Version

html-snippets
abu
0.2.1

aessoft-class-autocomplete
AES
0.1.0

project-manager
ale
8.0.0

vscode-angular2-files
ale
1.6.2

ng-template
Ang
0.1.10

typings-installer
ben
0.2.0

git-easy
bib
1.9.1

npm-intellisense
chr
1.3.0

path-intellisense
chr
1.4.2

vscode-eslint
dba
1.6.0

jquerysnippets
don
0.0.1

vscode-generate-getter-setter
DSK
0.5.0

vscode-html-css
ecm
0.2.0

EditorConfig
Edi
0.12.4

tslint
eg2
1.0.39

auto-close-tag
for
0.5.6

auto-rename-tag
for
0.0.15

vue-snippets
hol
0.1.9

beautify
Hoo
1.4.3

autofilename
Jer
0.1.3

docthis
joe
0.7.1

git-indicators
lam
2.1.1

node-module-intellisense
lei
1.5.0

vscode-emacs-friendly
lfs
0.8.2

vscode-language-pack-zh-hans
MS-
1.27.2

js-atom-grammar
ms-
0.1.14

debugger-for-chrome
msj
4.10.1

vetur
oct
0.12.6

ionic2-snippets
oud
1.0.0

vscode-css-peek
pra
2.1.0

LiveServer
rit
5.1.1

vscode-icons
rob
7.26.0

vscode-uppercase
rui
1.0.1

vue-vscode-snippets
sdr
1.3.0

code-settings-sync
Sha
3.1.2

autoimport
ste
1.5.3

ionic2
Tha
3.0.2

quokka-vscode
Wal
1.0.148

bootstrap-3-snippets
wcw
0.1.0

JavaScriptSnippets
xab
1.7.0

(2 theme extensions excluded)

@moontaicn Can you please explain more clearly what steps you are doing and what is happening vs what you expect?
When I am configuring the editor with:
"editor.wordWrap": "wordWrapColumn",
"editor.wordWrapColumn": 80,
"editor.rulers": [ 80 ],

I am seeing everything as expected:

authors: alexandrudima moontaicn


text:
Some key bindings conflict with those of the window manager

VSCode Version: 1.0.0
OS Version: Ubuntu 14.04 LTS, Cinnamon desktop environment

Steps to Reproduce:

Open more than one files on the side (so that the editor ends up with multiple columns)
Try using Ctrl+Alt+Shift+<Left/Right> to switch between editors

Expected behavior:
Editors are switched
Observed behavior:
Cinnamon intercepts the shortcut and switches workspaces instead
Is it possible to configure the editor's key bindings manually?

I do not think we can overwrite any of the OS taken keys. @alexandrudima ?

Each desktop environment "eats" different keybindings, it is almost impossible for us to have defaults that work in all Linux desktop environments.
@10098 I recommend customizing the keybindings via File > Preferences > Keyboard Shortcuts

authors: 10098 alexandrudima bpasero


text:
Support path alias Rename import path

With vscode 1.28 now we have Rename import path,
But it doesn't work with path aliases.
I tried to rename path with path alias like below
import('~/containers/DashboardPage')

But it's not allowed me to rename. Only shows some tooltip An error occured while resolving rename location
But when I changed to
import('./containers/DashboardPage')

It works well.
Here is my tsconfig.json for path settings.
"paths": {
  "~/*": ["*"]
}

Can you make it works with path aliases as well?

Thanks. Opened https://github.com/Microsoft/TypeScript/issues/27959 to track this upstream

authors: mjbvz rohmanhm


text:
Integrated terminal does not display accented character correctly

Issue Type: Bug
In the integrated terminal I see strings like "<81>" where accented chars ("ā" in this case) should be.
VS Code version: Code 1.28.0 (431ef9da3cf88a7e164f9d33bf62695e07c6c2a9, 2018-10-04T16:40:40.180Z)
OS version: Darwin x64 18.0.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-7567U CPU @ 3.50GHz (4 x 3500)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: enabledrasterization: enabledvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
2, 4, 4

Memory (System)
16.00GB (0.50GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (5)

Extension
Author (truncated)
Version

code-python-isort
fre
0.0.3

haml
kar
1.1.0

prettify-json
moh
0.0.3

python
ms-
2018.9.0

ruby
reb
0.20.0

Duplicate https://github.com/Microsoft/vscode/issues/60717

authors: Tyriar kirsis


text:
Did you run npm install?

Clone a new repo
Open in vscode
Tasks output panel pops up and says Running gulp --tasks-simple didn't list any tasks. Did you run npm install?
I didn't but I was just about to! Get off my back! 😁

This doesn't happen in stable, can this be less aggressive? Does it absolutely need to detect tasks when I haven't asked it to run a task yet?

We now detect tasks earlier because of automatic tasks. Based on this and other feedback we should not show anything in the output for automatic task issues!

This repo didn't have automatic tasks, this is the tasks.json: https://github.com/Microsoft/vscode-edge-debug/blob/master/.vscode/tasks.json#L1:L21

Pretty sure this is the repo where I saw it at least

Ended up being a duplicate of #64040


text:
Markdown: nested HTML not colored anymore

Refs: https://github.com/Microsoft/vscode/issues/7945
See:

See #7725.

authors: bpasero kieferrm


text:
Error: Error: spawn EACCES

VSCode Version: Version 1.3.1 (1.3.1)
OS Version: OS X 10.10.3

Steps to Reproduce:

change something in the file
Cmd + S

will see this error message.
https://cl.ly/2j2i30002k3P
Also tried to uninstall/reinstall VS Code but were never able to do a clean uninstallation.

@jimcal  can you please provide concrete steps that help us to recreate the issue? What's in your workspace? Do you have a sample workspace exhibiting the behavior? Which extensions have you installed? Does the same happen when you launch vscode with the --disable-extensions command line option? Thanks!

Well, the error is coming from extension, but I suspect the reason being Code didn't have proper permission. Would you be able to tell me how to give Code sudo permission?
To make this issue more relevant, perhaps you can also help me by uninstall Code cleanly and reinstall Code to see if this problem persist.

@jimcal
rm -rf ~/.vscode
rm -rf ~/Library/Application\ Support/Code

should remove all metadata on your Mac.

Thank you! Looks like reinstall clear the issue. I still think it's a permission issue and I don't know how to fix it without reinstall. I had my code worked in Sublime hence I would say it's about the IDE/editor than the Go code I had. Thanks for tips to removing the application metadata.

authors: jimcal kieferrm


text:
running as windows service works only if using the same account that executed config script

Running as windows service works only if using the same account that executed config script. If another account is used to run the service an exception is thrown (below).
2016-06-06 14:36:38Z ERR  AgentProcess] Internal.Cryptography.CryptoThrowHelper+WindowsCryptographicException: Keyset does not exist
at System.Security.Cryptography.CngKey.Open(String keyName, CngProvider provider, CngKeyOpenOptions openOptions)
at Microsoft.VisualStudio.Services.Agent.Listener.Configuration.RSACngKeyManager.GetKey() in D:\prj\vsts-agent2\src\Agent.Listener\Configuration\RSACngKeyManager.cs:line 97
at Microsoft.VisualStudio.Services.Agent.Listener.Configuration.OAuthCredential.<>c__DisplayClass2_0.b__0() in D:\prj\vsts-agent2\src\Agent.Listener\Configuration\OAuthCredential.cs:line 31
at Microsoft.VisualStudio.Services.WebApi.VssSigningCredentials.Create(Func1 factory)    at Microsoft.VisualStudio.Services.Agent.Listener.Configuration.OAuthCredential.GetVssCredentials(IHostContext context) in D:\prj\vsts-agent2\src\Agent.Listener\Configuration\OAuthCredential.cs:line 31    at Microsoft.VisualStudio.Services.Agent.Listener.Configuration.CredentialManager.LoadCredentials() in D:\prj\vsts-agent2\src\Agent.Listener\Configuration\CredentialManager.cs:line 56    at Microsoft.VisualStudio.Services.Agent.Listener.MessageListener.<CreateSessionAsync>d__12.MoveNext() in D:\prj\vsts-agent2\src\Agent.Listener\MessageListener.cs:line 64 --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at System.Runtime.CompilerServices.TaskAwaiter1.GetResult()
at Microsoft.VisualStudio.Services.Agent.Listener.Agent.d__11.MoveNext() in D:\prj\vsts-agent2\src\Agent.Listener\Agent.cs:line 166
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter1.GetResult()    at Microsoft.VisualStudio.Services.Agent.Listener.Agent.<ExecuteCommand>d__9.MoveNext() in D:\prj\vsts-agent2\src\Agent.Listener\Agent.cs:line 124 --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at System.Runtime.CompilerServices.TaskAwaiter1.GetResult()
at Microsoft.VisualStudio.Services.Agent.Listener.Program.d__2.MoveNext() in D:\prj\vsts-agent2\src\Agent.Listener\Program.cs:line 84

@patrickcarnahan - I think we agreed to store machine level correct?

I switched the key store to machine level and improved a bit the situation, but not completely. The "network service" account still gets the same exception "Key not found". However I'm able to run the service under a different account, just not "Network service" (for example config with domain account, run the service with an account I created locally on my box).

"Network service" account is restricted. I found an article on MSDN, that suggests how to grant read privilege for a certain key, but have not tried if it is going to work.

Fixed with https://github.com/Microsoft/vsts-agent/commit/cd23507341a55648d609914539b70fc4c3ced77d

authors: bryanmacfarlane stiliev

repo: Microsoft/vsts-agent


text:
get_storage_key function is under graph client and should be under identity client?

The get_storage_key function has
location_id='eb85f8cc-f0f6-4264-a5b1-ffe2e4d4801f'
when calling the function via a graph client (where the code is located) it returns a location error
grph_client.get_storage_key(usrDave.descriptor)
ValueError: API resource location eb85f8cc-f0f6-4264-a5b1-ffe2e4d4801f is not registered on https://aiz-alm.visualstudio.com.
-----------------Test w/ each client ------------------------

type(grph_client)
<class 'vsts.graph.v4_1.graph_client.GraphClient'>
type(id_client)
<class 'vsts.identity.v4_1.identity_client.IdentityClient'>

location_id='eb85f8cc-f0f6-4264-a5b1-ffe2e4d4801f'
grph_client._get_resource_location(location_id)
returns None

id_client._get_resource_location(location_id).dict
{'additional_properties': {}, 'id': 'eb85f8cc-f0f6-4264-a5b1-ffe2e4d4801f', 'area': 'Graph', 'resource_name': 'StorageKeys', 'route_template': '_apis/{area}/{resource}/{subjectDescriptor}', 'resource_version': 1, 'min_version': 3.2, 'max_version': 5.0, 'released_version': '0.0'}

This works for now - copied function from graph.py and now pass in two clients
def get_storage_key(id_client, grph_client, subject_descriptor):
"""GetStorageKey.
[Preview API] Resolve a descriptor to a storage key.
:param str subject_descriptor:
:rtype: :class:<GraphStorageKeyResult> <graph.v4_1.models.GraphStorageKeyResult>
"""
route_values = {}
if subject_descriptor is not None:
route_values['subjectDescriptor'] = id_client._serialize.url('subject_descriptor', subject_descriptor, 'str')
response = id_client._send(http_method='GET',
location_id='eb85f8cc-f0f6-4264-a5b1-ffe2e4d4801f',
version='4.1-preview.1',
route_values=route_values)
return grph_client._deserialize('GraphStorageKeyResult', response)

The resource area id is missing on the graph client.  It should be: BB1E7EC9-E901-4B68-999A-DE7012B920F8

fixed in #133

Thanks. I'll give it a try
On Tue, Oct 23, 2018, 12:26 PM Ted Chambers notifications@github.com
wrote:

fixed in #133
https://github.com/Microsoft/azure-devops-python-api/pull/133
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/azure-devops-python-api/issues/123#issuecomment-432317042,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAfLOl1xUdZXfLJpd75rC0QU3i1PzRGpks5un0MogaJpZM4W83mC
.

I have published a new version with the fix:
https://github.com/Microsoft/azure-devops-python-api/releases/tag/0.1.19

authors: tedchamb williware

repo: Microsoft/vsts-python-api


text:
NuGetPublisher task fails if server url has a space

Visual Studio Team Foundation Server 2015 Update 3 (On Premise) 14.102.25423.0
VSO Agent 14.102.25423.0
NuGetPublisher 0.1.41
I created a new service endpoint with a "Server URL" that has a space in it.
For example, http://mynugetserver:81/nuget/Dev Branch/.
But when I tried to use the "NuGet Publisher" build step to push a nupkg file to that endpoint, I get the error push: invalid arguments..
Here is the complete log for the "Nuget Publisher" build step:
    2017-04-26T21:53:36.2002567Z Set workingFolder to default: C:\agent\tasks\NuGetPublisher\0.1.41
    2017-04-26T21:53:36.2052530Z Executing the powershell script: C:\agent\tasks\NuGetPublisher\0.1.41\NuGetPublisher.ps1
    2017-04-26T21:53:36.5498772Z Check/Set nuget path
    2017-04-26T21:53:36.5518732Z Creating Nuget Arguments
    2017-04-26T21:53:36.5938304Z Checking server url set
    2017-04-26T21:53:36.5988244Z Checking server key set
    2017-04-26T21:53:36.5998246Z Pattern found in solution parameter.
    2017-04-26T21:53:36.6008239Z Find-Files -SearchPattern c:\agent\_work\4\s\CommonLibs\OUTPUT\Win32\Release\*.nupkg
    2017-04-26T21:53:36.6098121Z Found files: 1
    2017-04-26T21:53:36.6138081Z File: c:\agent\_work\4\s\CommonLibs\OUTPUT\Win32\Release\Common.1.0.0.nupkg
    2017-04-26T21:53:36.6168048Z Invoking nuget with push "c:\agent\_work\4\s\CommonLibs\OUTPUT\Win32\Release\Common.1.0.0.nupkg" -s http://mynugetserver:81/nuget/Dev Branch/ ******** on c:\agent\_work\4\s\CommonLibs\OUTPUT\Win32\Release\Common.1.0.0.nupkg
    2017-04-26T21:53:36.6178034Z C:\agent\agent\worker\tools\NuGet.exe push "c:\agent\_work\4\s\CommonLibs\OUTPUT\Win32\Release\Common.1.0.0.nupkg" -s http://mynugetserver:81/nuget/Dev Branch/ ********
    2017-04-26T21:53:37.3589981Z push: invalid arguments.
    2017-04-26T21:53:37.3869653Z usage: nuget push <package path> [API key] [options]
    2017-04-26T21:53:37.3879628Z Pushes a package to the server and publishes it.
    2017-04-26T21:53:37.3889621Z NuGet's default configuration is obtained by loading %AppData%\NuGet\NuGet.config, then loading any nuget.config or .nuget\nuget.config starting from root of drive and ending in current directory.
    2017-04-26T21:53:37.3899625Z      Specify the path to the package and your API key to push the package to the server.
    2017-04-26T21:53:37.3899625Z options:
    2017-04-26T21:53:37.3909615Z  -Source                (src)                                Specifies the server URL. If not specified, nuget.org is used unless DefaultPushSource config value is set in the NuGet config file.
    2017-04-26T21:53:37.3919600Z  -ApiKey                                                     The API key for the server.
    2017-04-26T21:53:37.3929570Z  -Timeout                                                    Specifies the timeout for pushing to a server in seconds. Defaults to 300 seconds (5 minutes).
    2017-04-26T21:53:37.3939582Z  -DisableBuffering                                           Disable buffering when pushing to an HTTP(S) server to decrease memory usage. Note that when this option is enabled, integrated windows authentication might not work.
    2017-04-26T21:53:37.3939582Z  -Help                  (?)                                  help
    2017-04-26T21:53:37.3949581Z  -Verbosity                                                  Display this amount of details in the output: normal, quiet, detailed.
    2017-04-26T21:53:37.3959559Z  -NonInteractive                                             Do not prompt for user input or confirmations.
    2017-04-26T21:53:37.3969541Z  -ConfigFile                                                 The NuGet configuration file. If not specified, file %AppData%\NuGet\NuGet.config is used as configuration file.
    2017-04-26T21:53:37.3979526Z For more information, visit http://docs.nuget.org/docs/reference/command-line-reference

I tried to update the service endpoint configuration and enclose the path with double quotes but I get the error message The Url specified for parameter endpoint.Url is not valid. Parameter name: endpoint.Url.
I tried to use %20 instead of the space such as http://mynugetserver:81/nuget/Dev%20Branch/ but it automatically gets replaced by a space when it's saved after I click the OK button, as the result is the same.
I tried to use a newer version of NuGet.exe and specify its path in the "NuGet Publisher" build step, but I get an unrelated error Ambiguous option 's'. Possible values: Source SymbolSource SymbolApiKey.
I'm not sure if this version is still being maintained or would I have to update to TFS 2017 in order to get the latest build agent?
Thank you.

This is fixed by #4397. If you want this update in your TFS server at its current version, wait for that PR to complete, then you should be able to build the task and then use the tfx-cli to install it to your server. Otherwise, yes, I believe you'd need to update to TFS 2017 or later to get the new tasks. @bryanmacfarlane can you confirm?

authors: alexmullans icnocop

repo: Microsoft/vsts-tasks


text:
Process 'msbuild.exe' exited with code '-1' (again!)

VSTS appears to be mainly resolved from this issue - however we have seen 2 failures of this status again in the last 24 hours.  Not sure if it's coincidence or not but both were the first build of each definition of the day, and both occurred about 60 seconds into msbuild.exe running on the first build task.  Any further insight @chrisrpatterson  @bryanmacfarlane ?
Just had a second build fail on the second build task with the same -1 code. (that's a 3rd failure)

reopen the original issue.

authors: bryanmacfarlane rposener


text:
Integration Test - Release - 2022/04/12 15:40:28

Auto create for integration test. IssueCommandFlow

Docs Build status updates of commit da27980:
:warning: Validation status: warnings

File
Status
Preview URL
Details

csidevdocs-public/IntegrationTest/BuildIntegrationTestFiles/ChangeSentToAuthor.md
:warning:Warning

Details

csidevdocs-public/IntegrationTest/BuildIntegrationTestFiles/ChangeSentToAuthor.md

Line 4, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 4, Column 8: [Warning: duplicate-titles - See documentation] Title 'VS Code Authoring Extension' is duplicated in: 'Demo/demo.md(4,8), Demo/v-caxian/AuthorNotification.md(4,8), Demo/v-caxian/auto-merge.md(4,8), Demo/v-caxian/auto-merger.md(4,8), IntegrationTest/BuildIntegrationTestFiles/ChangeSentToAuthor.md(4,8)'. Titles must be unique within a docset.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

source: gharchive/pull-request

repo: MicrosoftDocs/CSIDev-Public


text:
Integration Test - Release - 2022/06/28 11:10:37

Auto create for integration test. IssueCommandFlow

@prmerger-dev-1 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Docs Build status updates of commit 4571e47:
:warning: Validation status: warnings

File
Status
Preview URL
Details

csidevdocs-public/IntegrationTest/BuildIntegrationTestFiles/ChangeSentToAuthor.md
:warning:Warning

Details

csidevdocs-public/IntegrationTest/BuildIntegrationTestFiles/ChangeSentToAuthor.md

Line 4, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 4, Column 8: [Warning: duplicate-titles - See documentation] Title 'VS Code Authoring Extension' is duplicated in: 'Demo/demo.md(4,8), Demo/v-caxian/AuthorNotification.md(4,8), Demo/v-caxian/auto-merge.md(4,8), Demo/v-caxian/auto-merger.md(4,8), IntegrationTest/BuildIntegrationTestFiles/ChangeSentToAuthor.md(4,8)'. Titles must be unique within a docset.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


text:
Include File max side for file labeling, as well as max number of labels

We need to include that the max size for a file is 50MB here (it states there is a max size, but doesn't say what it is), as well as the max number of applies for an application is 100 per day.  this is crucial information that should be added here.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 9a3dc78f-a44c-de54-2a66-3f830345a90d
Version Independent ID: fdc60175-126c-a9a0-acd3-1f8e8c3b3263
Content: Troubleshooting content inspection errors - Cloud App Security
Content Source: CloudAppSecurityDocs/troubleshooting-content-inspection.md
Service: cloud-app-security
Product: ****
Technology: ****
GitHub Login: @shsagir
Microsoft Alias: shsagir

@gesmith-Ms Thanks for contacting Microsoft with feedback about our product documentation. Depending on the complexity, it could take from a few business days to a few weeks to look further into your question, issue, or suggestion. We'll contact you if we need further information, and you'll receive an email message each time we "@mention" you in a comment.
Thanks again for submitting your feedback. Your suggestions help improve our documentation.

@gesmith-Ms Thanks for your feedback. We've submitted a documentation change based on your suggestion, and the updated article should be live by tomorrow. Since labels are not related to this troubleshooting guide, it was not added but can be seen in the following topic: Azure Information Protection integration.
Please let us know if there's anything more we can do for you. To follow up on this issue, leave us a comment with an @mention.

authors: gesmith-Ms shsagir

repo: MicrosoftDocs/CloudAppSecurityDocs


text:
Show some samples with CreateFile over GetStdHandle

Originally from #93
I'm pretty sure we never show examples of using CreateFile with the CONIN$ and CONOUT$ special names to gain access to the underlying console (no matter what is in the standard handles). Or if we do... I don't think we go into much detail.
This represents documenting that fact/

Adding below all the locations I found where CONIN$ and CONOUT$ are documented after running a bing search:
https://docs.microsoft.com/en-us/windows/console/console-handles
https://docs.microsoft.com/en-us/windows/console/setstdhandle
https://docs.microsoft.com/en-us/windows/win32/api/fileapi/nf-fileapi-createfilea
https://docs.microsoft.com/en-us/windows/console/getstdhandle
https://docs.microsoft.com/en-us/windows/console/console-input-buffer
The solution can be to expand one of those locations with a code sample and then link to that location whenever the terms are mentioned elsewhere.
Github searches for the terms:
https://github.com/MicrosoftDocs/Console-Docs/search?q=CONIN
https://github.com/MicrosoftDocs/Console-Docs/search?q=CONOUT

repo: MicrosoftDocs/Console-Docs


text:
addition of the link to the resource

As mentioned by the user, I have updated added the link to point to the already available resource.
Problem:https://github.com/MicrosoftDocs/windows-itpro-docs/issues/6536

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks.

Thanks @JohanFreelancer9

repo: MicrosoftDocs/Devices-docs


text:
E1 user using computer used by a E3 user

Hello.
Let´s say we have a computer that is used by two user. User1 is licensed with E1 and User2 is licensed with E3. Will the User1 be able to use Office with full functionality as long as User2 refresh the grace period?
I guess its not possible but when I test this scenario, it seams to work that way. All thou I haven't tested for a longer period of time som I'm not sure.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: f3c236da-c63a-f789-f1b6-7aeb41f16c1f
Version Independent ID: 35319bac-d94f-832c-ce79-41bffe5c8d25
Content: Overview of licensing and activation in Office 365 ProPlus
Content Source: DeployOffice/overview-of-licensing-and-activation-in-office-365-proplus.md
Service: o365-proplus-itpro
GitHub Login: @DHB-MSFT
Microsoft Alias: danbrown

Does this end up being a violation of the license agreement?  Has there been a way found to resolve this issue?

I cannot answer any legal questions regarding the licensing agreement. I would ask that you contact your Microsoft account executive and they will put you in contact with a licensing executive.
From the technical aspect you will see after the E3 users activates office and the E1 user signs in that office says Belongs to the E3 users UPN. In Office 365 ProPlus version 1910 and greater this will not be an issue anymore based on the Licensing improvements mentioned in the above article.

authors: Craig-Lisovich MJP-MSFT toxarisswe

repo: MicrosoftDocs/OfficeDocs-DeployOffice


text:
Examples Missing Array Index

Some of the examples are missing the array index on the "Licenses" property
Get-MsolUser | Where-Object {$.isLicensed -eq $true -and $.Licenses.ServiceStatus[4].ProvisioningStatus -eq "Disabled"}

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: f403603f-e17b-8b5b-cbd8-8e4c6f4e1728
Version Independent ID: a93a3de1-25d3-4f7a-3e3e-3a6f25f88b75
Content: View account license and service details with Office 365 PowerShell
Content Source: Enterprise/powershell/view-account-license-and-service-details-with-office-365-powershell.md
Service: o365-administration
GitHub Login: @JoeDavies-MSFT
Microsoft Alias: josephd

@danmyhre The "long version" section with the incorrect examples has been removed. Thanks for letting us know.

Oh, it looks like this is the same issue I just reported, I apologize. Still there's not a correction of how that should be.
My query is the same as mentioned by @danmyhre but I'm using:
Get-MsolUser -All | where {$.isLicensed -eq $true -and $.Licenses[8].ServiceStatus[6].ProvisioningStatus -eq "Success"}
This is the result I get:
Cannot index into a null array.
At line:1 char:28

... ll | where {$_.isLicensed -eq $true -and $_Licenses[8].ServicesStatus ...

            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : InvalidOperation: (:) [], RuntimeException
FullyQualifiedErrorId : NullArray

authors: JoeDavies-MSFT c016smith danmyhre

repo: MicrosoftDocs/OfficeDocs-Enterprise


text:
IP adress updates

[Enter feedback here]
would you please update this IP address: 13.107.60.1/32  into https://docs.microsoft.com/en-us/office365/enterprise/urls-and-ip-address-ranges?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 077406d8-bff1-496e-3ea2-b38558fd9355
Version Independent ID: 57db3dec-2250-2dee-fd1a-ec6656911798
Content: Office 365 URLs and IP address ranges
Content Source: Enterprise/urls-and-ip-address-ranges.md
Service: o365-administration
GitHub Login: @JoeDavies-MSFT
Microsoft Alias: josephd

@Shane-zhao This IP address might be a Default category endpoint, which we don't explicitly list. Please see https://techcommunity.microsoft.com/t5/Office-365-Networking/Why-are-some-Office-365-network-endpoints-provided-as-URLs-only/m-p/310490#M97  for more information. Thanks for your comment.

authors: JoeDavies-MSFT Shane-zhao


text:
Add-on is not available for M365 Business Premium licenses

Seems the product team forgot that a M365 Business Premium license includes a SharePoint Plan 1.
In the current state customers with M365 Business Premium licenses are not able to order the add-on.

With this message the cause is unclear. But if a partner tries to order the add-on, then the system includes the required base offers.
Add-on can not be ordered without the corresponding base offer.
Please order one of the below base offers first:

- Microsoft 365 Business Standard
- Office 365 E1
- Office 365 E3
- Office 365 E5
- Microsoft 365 E3
- Microsoft 365 E5
- SharePoint (Plan 1)
- SharePoint (Plan 2)
- Microsoft 365 Business Basic

Please fix this.
Thanks
Tobias

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: e9aa1a91-e838-41c6-45cb-6a2a4dbf1a7a
Version Independent ID: 5f5c1b99-126f-2a70-20c8-f00136927e31
Content: Microsoft Syntex - SharePoint Advanced Management overview - SharePoint in Microsoft 365
Content Source: SharePoint/SharePointOnline/advanced-management.md
Service: sharepoint-online
GitHub Login: @MikePlumleyMSFT
Microsoft Alias: mikeplum

When will this be resolved? we're unable to purchase licenses.

For @scanum, I created support case 2304101420000716 on 10. April, but your colleagues don't believe it's an issue with M365 Business Premium license. I can prove this issue in several tenants. No recent update.

Still missing in M365 Business Premium licenses.

We (the documentation team) have reached out to the product group; we don't yet have updates from them that we can add to the article.
In the meantime, you're welcome to submit your feedback to the SharePoint Feedback Forum.

Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.

authors: TobiasAT YakovGoldberger scanum tiburd

repo: MicrosoftDocs/OfficeDocs-SharePoint