Terminal displays incorrect warning when we fail to parse a GUID #5752

Open
opened 2026-01-31 00:20:48 +00:00 by claunia · 0 comments
Owner

Originally created by @jagansankara on GitHub (Jan 2, 2020).

Environment

Windows build number:  Win32NT             10.0.18363.0 Microsoft Windows NT 10.0.18363.0
Windows Terminal version (if applicable): Version: 0.7.3451.0

Steps to reproduce

  1. Open profile.json file.
  2. Add new profile details.
  3. Save profile.json file

Sample file
profiles.json.txt

Expected behavior

Saved profile should be reflected in WT menu.

Actual behavior

Getting parsing error in Windows Terminal application even though setting is valid.
image

Originally created by @jagansankara on GitHub (Jan 2, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: Win32NT 10.0.18363.0 Microsoft Windows NT 10.0.18363.0 Windows Terminal version (if applicable): Version: 0.7.3451.0 ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> 1. Open profile.json file. 2. Add new profile details. 3. Save profile.json file Sample file [profiles.json.txt](https://github.com/microsoft/terminal/files/4016144/profiles.json.txt) # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> Saved profile should be reflected in WT menu. # Actual behavior <!-- What's actually happening? --> Getting parsing error in Windows Terminal application even though setting is valid. ![image](https://user-images.githubusercontent.com/10755858/71671836-147a6300-2d9a-11ea-9910-8aeb0845e952.png)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#5752