The opened "Azure Cloud Shell (Bash)" terminal looks a little ugly after switching Authentication Library

[v-ruizh]

OS: All
Build Version: 20211130.7
Regression: Not a regression

Repro Steps:

1. Set the "Azure: Authentication Library" setting to "ADAL".
2. Open a "Azure Cloud Shell (Bash)" terminal.
3. Change the "Azure: Authentication Library" setting to "MSAL"
4. Click "Sign Out and Reload Window" button in the opened notification to take effect Authentication Library change.
5. Check the above opened "Azure Cloud Shell (Bash)" terminal.

Expect:
The opened "Azure Cloud Shell (Bash)" terminal looks well.

Actual:
The opened "Azure Cloud Shell (Bash)" terminal looks a little ugly.

[wwlorey]

This also repros when you refresh the VS Code window without changing auth libraries.

I dug into this and unfortunately we can't do much about it ☹️ We provide aTerminalProfile to VS Code which it uses to create a Terminal. The problem is: once the terminal is created and the window refreshes we don't have access to that terminal from the extension so we can't catch this "socket hang up" error and show a better one.

[wwlorey]

Once VS Code supports opting out of persistent terminals we can fix this. We would just mark all of our terminals as non-persistent so when the window is refreshed that terminal is no longer shown. Tracking in microsoft/vscode#118726

[wwlorey]

This is coming soon: microsoft/vscode#139112