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

Register Flows in Azure Devops Build Pipeline throws UnicodeEncodeError #5754

Closed
NodeJSmith opened this issue May 5, 2022 · 1 comment
Closed

Comments

@NodeJSmith
Copy link
Contributor

Description

When using an Azure Devops pipeline for CI, registering a flow via a Python script fails due to an exception in the Client.register method.
image

I recognize that this does not sound like an issue with Prefect, but I do believe that the register method can be improved to avoid this bug. The issue stems from the 'prefix' variable used for message formatting at the end of the method. It is three unicode characters. If those could either be replaced or use a try/except and replace them if a UnicodeEncodeError is thrown, it would resolve the issue.

image

Expected Behavior

Expected behavior is that the flow is registered without any exception being raised.

Reproduction

Create a python script that uses Client class, and use the client to register a flow. Run this in an Azure DevOps build pipeline through a shell task or a powershell task.

Environment

Windows 2019 image
image
Included Software: https://github.com/actions/virtual-environments/blob/win19/20220503.1/images/win/Windows2019-Readme.md
Image Release: https://github.com/actions/virtual-environments/releases/tag/win19%2F20220503.1

Windows 2022 image
image
Included Software: https://github.com/actions/virtual-environments/blob/win22/20220503.1/images/win/Windows2022-Readme.md
Image Release: https://github.com/actions/virtual-environments/releases/tag/win22%2F20220503.1

@NodeJSmith
Copy link
Contributor Author

Closing this - after half of year of this niggling at the back of my head I was able to trace down the cause and have confirmed it is caused by the Windows agent and not by any Python library. I provided more information on this comment and I'm writing up a gist here with more details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant