Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gibberish and inconsistencies in package IDs #4491

Open
github-account1111 opened this issue May 17, 2024 · 4 comments
Open

Gibberish and inconsistencies in package IDs #4491

github-account1111 opened this issue May 17, 2024 · 4 comments
Labels
Area-Output Issue related to CLI output Issue-Bug It either shouldn't be doing this or needs an investigation.

Comments

@github-account1111
Copy link

Brief description of your issue

Some packages show up with gibberish sometimes, but not other times:

image

Makes it difficult to install based on --id.

Steps to reproduce

Search for a package using different word combinations.

Expected behavior

Id is the same every time and doesn't contain any gibberish.

Actual behavior

Id contains gibberish sometimes.

Environment

Windows Package Manager v1.7.11261
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.19045.4412
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.22.11261.0

Winget Directories
-------------------------------------------------------------------------------------------------------------------------------
Logs                               %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir
User Settings                      %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\settings.json
Portable Links Directory (User)    %LOCALAPPDATA%\Microsoft\WinGet\Links
Portable Links Directory (Machine) C:\Program Files\WinGet\Links
Portable Package Root (User)       %LOCALAPPDATA%\Microsoft\WinGet\Packages
Portable Package Root              C:\Program Files\WinGet\Packages
Portable Package Root (x86)        C:\Program Files (x86)\WinGet\Packages
Installer Downloads                %USERPROFILE%\Downloads

Links
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale

Admin Setting                             State
--------------------------------------------------
LocalManifestFiles                        Disabled
BypassCertificatePinningForMicrosoftStore Disabled
InstallerHashOverride                     Disabled
LocalArchiveMalwareScanOverride           Disabled
Copy link

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Triage Issue need to be triaged label May 17, 2024
@Trenly
Copy link
Contributor

Trenly commented May 18, 2024

It seems the inconsistencies are related to the console width and the ID's being truncated. In some fonts the character appears as ..., but depending on system settings the character code could be different, resulting in the à that you're seeing.

image

@microsoft-github-policy-service microsoft-github-policy-service bot added Area-Output Issue related to CLI output Issue-Bug It either shouldn't be doing this or needs an investigation. and removed Needs-Triage Issue need to be triaged labels May 18, 2024
@eabase
Copy link

eabase commented May 30, 2024

Yes, check your font and also make sure to use UTF-8. UTF8 should be on by default in Win-10/11 but if you messed with it...

@github-account1111
Copy link
Author

Yes, check your font and also make sure to use UTF-8. UTF8 should be on by default in Win-10/11 but if you messed with it...

Yes, I even made sure to make UTF-8 the default for all languages:

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Output Issue related to CLI output Issue-Bug It either shouldn't be doing this or needs an investigation.
Projects
None yet
Development

No branches or pull requests

3 participants