No Semantic Tokens are Being Generated, while the IntegratedTerminal is working

Prerequisites

• I have written a descriptive issue title.
• I have searched all issues to ensure it has not already been reported.
• I have read the troubleshooting guide.
• I am sure this issue is with the extension itself and does not reproduce in a standalone PowerShell instance.
• I have verified that I am using the latest version of Visual Studio Code and the PowerShell extension.

Summary

There are no semantic tokens being used by the editor. ( I was debugging why semantic colors for the powershell language was ignoring all semantic configurations. )

It’s supposed to look like this:

PowerShell Version

🐒> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      7.2.0
PSEdition                      Core
GitCommitId                    7.2.0
OS                             Microsoft Windows 10.0.19043
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Visual Studio Code Version

1.63.0
7db1a2b88f7557e0a43fec75b6ba7e50b3e9f77e
x64

code.cmd --list-extensions --show-versions | select-string powershell

Extension Version

ms-vscode.powershell@2021.10.2

Steps to Reproduce

1. Enable semantic in your settings.json
2. Open any *.ps1 file .1 Use token inspector, and you get no info.

semantic config

I have every possible semantic config enabled.

Visuals

I think the Language Server is running

This screen shows that these are all running

• autocomplete
• 1 reference
• ScriptAnalyzer warnings

Logs

{
    "csharp.semanticHighlighting.enabled": true, // default is false?
    "editor.semanticHighlighting.enabled": true, //     // <true | false | ConfiguredbByTheme>
    "editor.semanticTokenColorCustomizations": {
        "csharp.semanticHighlighting.enabled": true, // default is false?
        "editor.semanticHighlighting.enabled": "true",
        "editor.semanticTokenColorCustomizations": {
            // per-theme
            "enabled": true,
            "rules": {
                "parameter": {
                    "foreground": "#ea00ff",
                    "underline": true,
                    "bold": true,
                    "italic": true,
                    "fontStyle": "italic bold underline"
                },
            },
            "[Default Dark+]": {
                "enabled": true,
                "rules": {
                    // single value
                    // vs many
                    "*.abstract": {
                        "foreground": "#0000ff",
                        "underline": true,
                        "fontStyle": "bold underline"
                    },
                    "parameter": {
                        "foreground": "#ea00ff",
                        "underline": true,
                        "bold": true,
                        "italic": true,
                        "fontStyle": "italic bold underline"
                    },
                }
            },
        },
    }
}

[ninmonkey]

Working

Addon	Version	Code	Version
ms-vscode.powershell	2021-10-02	insider	‘1.64.0-insider’, ‘d12df34e31b4a018735d312a8947d79331132368’, ‘x64’
ms-vscode.powershell-preview	2021-11-01	insider	‘1.64.0-insider’, ‘d12df34e31b4a018735d312a8947d79331132368’, ‘x64’

Failed

Addon	Version	Code	Version
ms-vscode.powershell	2021-06-01	code	‘1.63.0’, ‘7db1a2b88f7557e0a43fec75b6ba7e50b3e9f77e’, ‘x64’
ms-vscode.powershell	2021-10-02	code	‘1.63.0’, ‘7db1a2b88f7557e0a43fec75b6ba7e50b3e9f77e’, ‘x64’
ms-vscode.powershell-preview	2021-11-01	code	‘1.63.0’, ‘7db1a2b88f7557e0a43fec75b6ba7e50b3e9f77e’, ‘x64’

Since code is failing but powershell-preview and powershell both work correctly on code-insiders, I’ll close this as resolved.

[andschwa]

Oh awesome, thanks so much @ninmonkey!