text:
"Auto Sync is disabled."

Second day cant use a sync. When i try to enable Sync and auth by Microsoft account i get this
[2021-01-13 18:16:00.915] [userDataSync] [info] Using settings sync service https://vscode-sync.trafficmanager.net/
[2021-01-13 18:16:00.915] [userDataSync] [info] Auto Sync is disabled.
[2021-01-13 18:27:40.879] [userDataSync] [info] Request failed {"url":"https://vscode-sync.trafficmanager.net/v1/manifest","status":401,"execution-id":"44b9d786-bef6-484e-b276-2335fdf1d44f","operation-id":"0a38a25e890748bdb688afed7b60df83"}

/duplicate of #114231

/duplicate of #114231

authors: IllusionMH lostcodder


text:
Add an api for extensions to detect/observe Zen mode

It would be nice for extensions to be able to adapt when Zen mode is active.
Refs: https://github.com/eamodio/vscode-gitlens/issues/1338

@eamodio this makes good sense! Let's see if there are more extensions that would benefit from this and if yes we could look into adding this.

@eamodio this makes good sense! Let's see if there are more extensions that would benefit from this and if yes we could look into adding this.

@isidorn This would be really useful for extensions that create distractions when screen recording.

I'm developing a plug-in for reading novels. It can enter full screen to get a better reading experience, but the header in zen mode still takes up a little space. Now I want to use it, such as displaying the time and title, but I have no way of knowing whether the user is currently in zen mode, the user can either through the plugin api, or through a keyboard shortcut, so I also need a way to detect zen mode

source: gharchive/issue

repo: microsoft/vscode

license: MIT

license_type: permissive

license_source: github-api


text:
No autosuggestion / autocompletion for Chinese variables / identifiers

VS Code Version: 1.54
OS Version: Windows 10 1909

I am using lots of Chinese variables in writing Python codes, but early this month, I found these is no more autosuggestion / autocompletion for variables / identifiers started with Chinese character. I suspect it might be caused by the update of Code, so I tried older version (1.51), but the problem persists.
Same problem is encountered by programmers using Chinese variables like me. This is very upsetting. Please fix it. Thanks.

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

@laowu2019 this is a problem with the Python extension you are using. Please report the issue there since VS Code out of the box has no Python code complete support.


text:
macOS entitlements and entries for Info.plist disallow developing and running certain types of apps via VSCode

VS Code Version: 1.54.3
OS Version: macOS 10.15.7 (19H524)

Steps to Reproduce:

macOS specific
Develop a project in VSCode that somewhere down the chain uses call to NSAppleScript. In my case it is an Electron project that spawns multiple native binaries written in Swift where one of them uses NSAppleScript and pipes data between Electron main process and native runtime.
Run the project through VSCode terminal (in my case it is live reloading Electron project).
macOS security system will not ask user permission to allow access for VSCode to some other apps AE dictionary.
Yes, VSCode, not the app developed via VSCode, because VSCode encapsulates the process and spawned subprocesses, it is the main bundle in this case.

When some process wants to access AE dictionaries for other apps a permission to macOS is asked which in turn results in permissions dialog represented to user. Permission can be denied or granted, and the entry with chosen allowance will show up in Automation anchor under System preferences : Security & Privacy.
In order for this to work the bundle that encapsulates the runtime that uses AE has to have

entitlement
<key>com.apple.security.automation.apple-events</key>
<true/>

Info.plist entry
<key>NSAppleEventsUsageDescription</key>
<string>Bla bla</string>

N.B. Entries NSAppleScriptEnabled and OSAScriptingDefinition are different beasts.

Due to VSCode entitlements and Info.plist settings the call will not go through, that is - process running in VSCode terminal will not signal macOS gatekeeper that permission to access specific app AE is asked, user (in this case a developer using VSCode) will not be notified, System preferences : Security & Privacy : Automation will not populate, and app development/debugging cannot happen.
Note that current VSCode setup passes through subprocesses that need Accessibility and Screen Recording permissions (I use them in my binaries, too) -  System preferences : Security & Privacy anchors Accessibility and Screen Recording will populate. Not relevant to me, but I imagine that other permissions under com.apple.security.* cases might fail Apple docs on Hardened Runtime

IMHO, VSCode should open up permissions as its terminal serves for live debugging apps that may ask different kind of permissions to OS. Due to the very nature of VSCode I consider this to be a bug not missing feature.

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

Thanks for the detailed issue report, this is another variation of https://github.com/microsoft/vscode/issues/95062. I haven't enabled these entitlements mainly because of the permission model around it, once a user grants these permissions to the app it is not only gonna help the terminal process but also other untrusted processes, specifically in our case the extension process. Say for example a bad extension wants to use some apple events or media device access, to a user the permission dialog will only mention that vscode wants this permission, there is no way to intercept this flow currently within vscode and explicitly tell the user who is asking for it and why.
Alternatively if I can enable these entitlements on a particular helper executable and not for the app, it would also allow some granularity to control these permissions for the app. It is unfortunate that the vscode terminal is expected to behave as the OS terminal but the permissions are tied down because of the app. I am happy to explore solutions that would not give the extension process these privileged entitlements.
Is it not possible to execute your app from the vscode terminal using the Launchservice (ex: open) that would ensure the app process is not related to vscode.

Thanks for your time!
Security was on my mind

permission dialog will only mention that vscode wants this permission
hence I mentioned that Accessibility and Screen Recording passes though. It already is a game where if user trusts VSCode in those areas, then the user is stripped naked for a rogue processes, be extensions or from within terminal. I can get all the data about user activity, mouselog, keylog via VSCode (via other means than AE, NSEvent.addGlobalMonitorForEvents, NSWorkspace.shared.notificationCenter observers, CoreGraphics and other beasts), I know that first hand - the very Electron app I develop spawns native binaries that I have written that do that by design.

Having those permissions already open probably is not a strong argument for enabling AE access, enabling yet another potential attack type via VSCode. I understand and respect your stance that VSCode has to do everything it can to protect the developer from malicious extensions, although I do not necessarily agree with it. I would set that responsibility on developer to choose wisely, disallowing AE is like shutting down pet door to an house while leaving open all the other doors, garage and windows.

Alternatively if I can enable these entitlements on a particular helper executable and not for the app, it would also allow some granularity to control these permissions for the app. I am happy to explore solutions that would not give the extension process these privileged entitlements.

I will think about it. For example macOS 11 now comes with some new ways of doing things regarding permissions, but still the API regarding reading, asking for and self-disalowing is still unfinished. If there was a solution it would be hacky, I'm pulling my hair out how unfinished and rushed things are from Apple side for security-related APIs since changes in 10.15.
One instant idea that comes into mind is tccutil. tccutil reset AppleEvents com.microsoft.VSCode on every launch, thus every developer session in VSCode gets flushed permissions for AppleScript (and tccutil reset ScreenCapture, tccutil reset Accessibility too).
Other idea is that VSCode implements yet another "helper" - a custom app bundle that sits along Code Helper.apps, call it SecurityHelper.app. It would be some kind of middleware - it exposes endpoint that must be used by any extension that wants to call applescript, extension sends in serialised json containing whoami and eastringtoexecute, middleware decides to execute or not and if yes does that and returns result. Then again - so much stuff to do for only one platform and only one potential attack vector while all others are open.
Hopefully you will not close this ticket, let it marinate a bit.

Sorry for the delayed response, we had discussed this internally and decided to enable the following entitlements.
com.apple.security.automation.apple-events
com.apple.security.device.camera
com.apple.security.device.audio-input

Thank you! Apart from entitlements

https://github.com/microsoft/vscode/pull/119788 adds NSAppleEventsUsageDescription to Info.plist
NSCameraUsageDescription and NSMicrophoneUsageDescription already are inherited by VSCode from Electron base.

They could be reformulated though for uberclarity if one knows that VSCode itself will not use those features

Given that these access in most situations are performed under a user triggered action in the terminal or extension they have installed, I don't think we need to be specific in the wording and just follow suite of what other mac apps do.

FYI to reset permissions programmatically (which would allow VSCode to have a menu entry under Preferences or Help to disallow itself)

I don't think we want to add these helpers to the app. A user should just default to the OS for clearing these permissions and not look for way to do it from within the app.

/verified 🔥

authors: deepak1556 kroko paulvonallwoerden


text:
Document new colors

The following colors need to be documented at https://raw.githubusercontent.com/microsoft/vscode-docs/vnext/api/references/theme-color.md

[ ] "button.border: Button border color." @aeschli
[ ] ~"editorInlineHint.foreground: Foreground color of inline hints" @jrieken~
[ ] ~"editorInlineHint.background: Background color of inline hints" @jrieken~
[x] "toolbar.hoverBackground: Toolbar background when hovering over actions using the mouse" @joaomoreno @roblourens
[x] "toolbar.hoverOutline: Toolbar outline when hovering over actions using the mouse" @joaomoreno
[x] "toolbar.activeBackground: Toolbar background when holding the mouse over actions" @joaomoreno @roblourens
[ ] ~"workspaceTrust.trustedForegound: Color used when indicating a workspace is trusted." @sbatten~
[ ] ~"workspaceTrust.untrustedForeground: Color used when indicating a workspace is not trusted." @sbatten~
[ ] ~"workspaceTrust.tileBackground: Background color for the tiles on the Workspace Trust page." @sbatten~
[x] "ports.iconRunningProcessForeground: The color of the icon for a port that has an associated running process." @alexr00

removing myself because the inlineHint colours aren't consumable yet

same for me, the trust options need work

FYI @jrieken @sbatten -- the endgame plan contains a bullet point that asked me to create this issue. It is very likely that the next endgame champion will ping you again (unless the tool is adjusted somehow).

I know. You are not the first endgame master to ping me 😄

authors: alexdima jrieken sbatten


text:
unbound breakpoint for Angular project

I just created a new Angular project per (https://code.visualstudio.com/docs/nodejs/angular-tutorial), but once I click green debug and run button, all breakpoints became unbound. beside that, the app run well.

I have tried downgrade vscode to 1.55, tried javascript debug nightly, tried install/uninstall debugger for chrome
thanks, appreciate your help
vscode-debugadapter-3a110541.json.gz

You have Angular running in a subdirectory, so you want to set webRoot to ${workspaceFolder}/ng-battleship

got it. thanks.
On Wed, Jul 7, 2021 at 3:29 PM Connor Peet @.***> wrote:

You have Angular running in a subdirectory, so you want to set webRoot to
${workspaceFolder}/ng-battleship
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/128141#issuecomment-875872896,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANA576PG3V2XMYAA7G4TT3LTWSTIRANCNFSM4766I6DA
.


text:
[Inlay hints] Enforce minimal text contrast

Theme to reproduce: https://marketplace.visualstudio.com/items?itemName=usernamehw.prism

Version: 1.60.0-insider (user setup)
Commit: 1ee61f368ee0570feeb220605578a8768d99e762
OS: Windows_NT x64 10.0.19043

@misolori Can you help me find good colors for inlay hints? Currently, there is three kinds: inlay hints for types, for arguments/parameters, and others.
Also related to https://github.com/microsoft/vscode/issues/133673

All of those colors are using the same default for editorInlayHint so you are good there. Looking at other light themes, most seem to look good there's just a few that don't look great. This is where those themes need to define the colors using those tokens as we won't be able to find colors that perfectly match every theme.

Thanks @misolori

authors: jrieken misolori usernamehw


text:
Extension properties' scope: machine attr have behavior that's different with the docs

VS Code Version: yarn web, or server-linux-x64-web
OS Version: Fedora 34

Docs says:

machine - Machine specific settings that can be set in user or remote settings. For example, an installation path which shouldn't be shared across machines.

But these code prohibited me to set properties in User setting scope:
https://github.com/microsoft/vscode/blob/892785264b4682d102b9cb81e01a549c218a74ee/src/vs/workbench/contrib/preferences/browser/preferencesRenderers.ts#L550-L559
( I am not very familiar with VSCode, hoping "User setting scope" this name is correct ):

So is this behavior in design? Why? Docs says "can be set in user or remote settings", but now it only could be set in Remote setting scope.

An example: create a extension with machine scope prop:
"myextension.cfg1": {
  "type": ["string"],
  "scope": "machine",
  "default": null
}

Then set this prop on Web UI, you will see:
This setting cannot be applied in this window. It will be applied when you open a local window.

Doc needs to be updated - Configuration that can be configured only in the user settings or only in the remote settings

@sandy081 You say only in the user settings or only in the remote settings, but still does not match the current implementation 😂
The result of my test is only in the remote settings, but NOT in the user settings. Although remote setting not be set, user setting value still be ignored. That's why I think it's unreasonable.
If you still think that this impl is true, ╮(╯▽╰)╭ ,I have nothing to say.

We mean "in a local window, only in user settings. In a remote window, only in remote settings". It's typically a setting that has something like a path that only has meaning on the actual machine where a workspace extension runs.

authors: kkocdko roblourens sandy081


text:
Issue reporter does nothing when "Create on GitHub" is pressed

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

VS Code Version:
1.60.2
OS Version:
Windows 11 x64 22000

Steps to Reproduce:

Help -> Report Issue
Fill out the report as shown:

Click "Create on GitHub"
(nothing happens)

Signing out and signing back in does not fix the already-open issue reporter, and the already-open issue reporter has captured information about my extension bisect that I lose when I close it (the bisect is how I ended up in the Issue Reporter). Also when I close and re-open the Issue Reporter, the extension is disabled (automatically, as a result of it being the culprit that the extension bisect discovered). So, this workaround isn't ideal and it might be the case that bug reports are just not getting filed by the extension bisect tool (which is fantastic, btw).

@0xabu was unable to reproduce on 1.84.2

authors: 0xabu altano justschen