Fix: Replace emojis with ASCII alternatives to fix GBK encoding issues (issue #2628) #2629
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR fixes issue #2628 by replacing emojis in the console formatter with ASCII alternatives to prevent blocking errors with GBK encoding on Windows systems.
Problem
Emojis in the codebase were causing blocking errors when using GBK character encoding (commonly used on Windows systems, especially for Chinese users). This made CrewAI unusable for some Windows users.
Solution
console_formatter.pywith ASCII alternatives that are compatible with GBK encodingEmoji Replacements
Testing
Added a test that verifies the console formatter output can be encoded with GBK without errors.
Closes #2628
Link to Devin run: https://app.devin.ai/sessions/f38ae3bd18794b4181bf360c6b77a68a
Requested by: Joe Moura (joao@crewai.com)