UUID generation example looks wrong

[vblazhkun]

In the given text the UUID generation example of:

• UUID Version: 5
• Namespace UUID: {2BDE4A90-D05F-401C-9492-E40884EAD1D8}
• Text: Ubuntu

Leads to UUID of {2C4DE342-38B7-51CF-B940-2309A097F518} which does not match to what we have with the standard RFC4122 implementations:

$ uuid -v 5 '2BDE4A90-D05F-401C-9492-E40884EAD1D8' 'Ubuntu'
8fa9feba-8e6e-5128-a6ba-e0926db2a4b4

$ ipython
IPython 7.30.1 -- An enhanced Interactive Python. Type '?' for help.
                                                                    
In [1]: import uuid                                                 
                                                                    
In [2]: u = uuid.UUID('{2BDE4A90-D05F-401C-9492-E40884EAD1D8}')     
                                                                    
In [3]: u                                                           
Out[3]: UUID('2bde4a90-d05f-401c-9492-e40884ead1d8')                
                                                                   
In [4]: uuid.uuid5(u, 'Ubuntu')                                     
Out[4]: UUID('8fa9feba-8e6e-5128-a6ba-e0926db2a4b4')

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: e7dd918e-788a-e3f5-379f-240d72b1e6ea
• Version Independent ID: 341f8755-2701-601f-5b91-98527354b3e8
• Content: Windows Terminal JSON Fragment Extensions
• Content Source: TerminalDocs/json-fragment-extensions.md
• Product: dev-environment
• Technology: windows-terminal
• GitHub Login: @cinnamon-msft
• Microsoft Alias: cinnamon

[Okeanos]

I think this is a duplicate of #320 (to be solved by #460).

[mattwojo]

Just merged the fix: #460

Thanks @vblazhkun (and thanks @Okeanos for the fix!)