microsoft/Terminal

Default profile can point to one deleted in state.json

Open

#14,420 opened on Nov 21, 2022

View on GitHub
 (4 comments) (0 reactions) (0 assignees)C++ (3,212 forks)batch import
Area-SettingsHelp WantedIssue-BugPriority-3Product-Terminal

Repository metrics

Stars
 (35,764 stars)
PR merge metrics
 (Avg merge 27d 19h) (24 merged PRs in 30d)

Description

Windows Terminal version

1.17.2982.0

Windows build number

25236.1010

Other Software

PowerShell (potentially caused by multiple versions installed?)

Steps to reproduce

  1. Open Windows Terminal (see PowerShell Core profile)
  2. Open new tab (different PowerShell profile appears)

Helpful info

settings.zip

defaultProfile is set to a legacy version of powershell core. However, that profile doesn't exist anymore. It's interesting that...

  1. resolving it on startup results in a different profile than when hitting the new tab button
  2. I can't seem to edit that profile? It doesn't seem like it's hidden. Idk why it still resolves correctly?

Expected Behavior

Both tabs should contain the same profile

Actual Behavior

Both tabs have different profiles.

Contributor guide

Research direction
Examine how defaultProfile is resolved from state.json and compare with the profile resolution when opening a new tab. Trace the code paths for both scenarios to understand why they differ.
Tech stack
cpp
Domain
desktop
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60