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

2-byte languages cannot be entered in the Start block #9663

Closed
5 tasks done
atakamizawa opened this issue Oct 22, 2024 · 2 comments · Fixed by #9672
Closed
5 tasks done

2-byte languages cannot be entered in the Start block #9663

atakamizawa opened this issue Oct 22, 2024 · 2 comments · Fixed by #9672
Assignees
Labels
🐞 bug Something isn't working
Milestone

Comments

@atakamizawa
Copy link

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:)
  • Please do not modify this template :) and fill in all the required fields.

Dify version

0.10.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

2-byte languages cannot be correctly entered in the START block. It behaves as if characters that have only been entered once appear multiple times.
This problem does not occur after Start Chat, so I believe this is an issue that only arises at the very beginning of starting the app.
The attached gif shows the behavior when trying to enter "test message" in Japanese.
0 10 0

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

@dosubot dosubot bot added the 🐞 bug Something isn't working label Oct 22, 2024
@crazywoola crazywoola added this to the 0.10.1 milestone Oct 23, 2024
@atakamizawa
Copy link
Author

I'm sorry for submitting an incomplete issue. Thank you for addressing it.

@kurokobo
Copy link
Contributor

@atakamizawa
Oh, I'm sorry too, I opened a duplicate issue. I couldn't find this properly while searching: #9671

This issue should be fixed in my PR #9672, so I hope it gets merged 😌

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.

4 participants