unicode issue in 2.4.1, published variable in workflow is not as expected to next task.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
after updated to version 2.4.1, we're encountering unicode issue again.
in mistral workflow, what has been published in previous task is not as expected to next tasks.
say if we have publish a Chinese character in task1, but it seems has been encode as input to the next task.
I attached tested code FYI (you can put them to pack: examples)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by unpacking leo-test-unicode.zip and placing the included files in the examples pack, then reproduce the Mistral workflow with a Chinese character published by one task. Trace how the published value is passed to the next task; done means the downstream task receives the original Unicode character rather than an encoded value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100