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

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 #216

Closed
horihiro opened this issue Apr 6, 2022 · 6 comments · Fixed by #221
Labels
bug Something isn't working

Comments

@horihiro
Copy link

horihiro commented Apr 6, 2022

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:
image

@horihiro horihiro added the need-to-triage Requires investigation label Apr 6, 2022
@horihiro horihiro changed the title Erro "Unable to encode the output with cp1252 encoding." Error Unable to encode the output with cp1252 encoding. is shown when logging in to a subscription which name contains non-ASCII characters and on Windows runner Apr 6, 2022
@horihiro horihiro changed the title Error Unable to encode the output with cp1252 encoding. is shown when logging in to a subscription which name contains non-ASCII characters and on Windows runner 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 Apr 6, 2022
@horihiro
Copy link
Author

horihiro commented Apr 8, 2022

@BALAGA-GAYATRI could you please take a look at this or assign anyone?

@BALAGA-GAYATRI
Copy link
Contributor

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

@BALAGA-GAYATRI BALAGA-GAYATRI added question The issue doesn't require a change to the product in order to be resolved. Most issues start as that bug Something isn't working and removed need-to-triage Requires investigation question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Apr 11, 2022
@horihiro
Copy link
Author

Hello @BALAGA-GAYATRI
I did addional check by the following job.

jobs:
  login:
    runs-on: windows-latest
    steps:
    - run: |
        az login --service-principal -u ${{ secrets.AZURE_CLIENT_ID }} -p ${{ secrets.AZURE_CLIENT_SECRET }} --tenant ${{ secrets.AZURE_TENANT_ID }}

Then, the job was succeeded, even though the same warning message WARNING: Unable to encode the output with cp1252 encoding. Unsupported characters are discarded. was shown.
image

From this result, it seems that the azure/login action and @action/exec module which is used in this action handle this warning as an error.
Could you please check this point?

@BALAGA-GAYATRI
Copy link
Contributor

Sure. Will check this out and let you know. Thanks for the extra insights.

@BALAGA-GAYATRI
Copy link
Contributor

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

@horihiro
Copy link
Author

horihiro commented May 4, 2022

Thanks @BALAGA-GAYATRI !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants