Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error `Unable to encode the output with cp1252 encoding.` is shown when logging in to a subscription which name contains Japanese characters and on Windows runner

See original GitHub issue

When trying to log in with a subscription which name contains Japanese characters by the following simple workflow, the logging in is failed with the encoding error like the following screenshot.

Workflow:

name: Azure Login Test

on:
  workflow_dispatch:

jobs:
  login:
    runs-on: windows-latest # using Windows runner
    steps:
    - uses: azure/login@v1
      with:
        creds: ${{ secrets.AZURE_CREDENTIALS }}

Error screenshot:

Issue Analytics

State:
Created a year ago
Comments:6

Top GitHub Comments

1reaction

BALAGA-GAYATRIcommented, May 4, 2022

Fixed this bug in v1.4.4 and updated azure/login@v1 with the latest release.

1reaction

BALAGA-GAYATRIcommented, Apr 11, 2022

@horihiro we shall look into this issue and let you know.

Top Results From Across the Web

Unable to encode the output with cp1252 encoding ... - GitHub

in a powershell console, the console window will return the message "Unable to encode the output with cp1252 encoding.

Unable to encode the output with cp1252 encoding ...

We have a release pipeline which invoke a powershell script task to call a file (.ps1) from Azure repo. Everything works fine for...

charmap error when encoding Japanese characters

You need to set the correct encoding when opening the file you're writing to, like such: with open('Translated.txt','w', encoding='utf-8') ...

Understanding file encoding in VS Code and PowerShell

This problem occurs because VS Code encodes the character – in UTF-8 as the bytes 0xE2 0x80 0x93 . When these bytes are...

Filename encoding and interoperability problems

Note that the invalid Unicode characters have been hex-encoded in this error message because otherwise trying to print them would result in another...