langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 12:05:30 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

The tool description in prompt is Ascii #4762

New Issue
Closed
opened 2026-02-21 18:07:54 -05:00 by yindo · 5 comments
yindo commented 2026-02-21 18:07:54 -05:00
Owner
Copy Link
Copy Source

Originally created by @401557122 on GitHub (Jul 24, 2024).

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).
  • 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

0.6.15

Cloud or Self Hosted

Self Hosted (Docker), Self Hosted (Source)

Steps to reproduce

May I ask why the tool information in the prompt is all in Ascii encoding format? Is this an error? I previously directly modified the secure_ascii=True parameter of the dump in my local JSON package to fix this issue. I would like to know if this is necessary

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @401557122 on GitHub (Jul 24, 2024). ### Self Checks - [X] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [X] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [X] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [X] Please do not modify this template :) and fill in all the required fields. ### Dify version 0.6.15 ### Cloud or Self Hosted Self Hosted (Docker), Self Hosted (Source) ### Steps to reproduce May I ask why the tool information in the prompt is all in Ascii encoding format? Is this an error? I previously directly modified the secure_ascii=True parameter of the dump in my local JSON package to fix this issue. I would like to know if this is necessary ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 📚 documentationstale labels 2026-02-21 18:07:54 -05:00
yindo closed this issue 2026-02-21 18:07:54 -05:00
yindo commented 2026-02-21 18:07:55 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jul 24, 2024):

The tool information in the prompt is in ASCII encoding format because the ensure_ascii parameter is set to True in the JSON serialization process. This is not an error but a deliberate setting in the codebase.

For example, in the unauthorized_handler function, the json.dumps method is used with ensure_ascii=True:

@login_manager.unauthorized_handler
def unauthorized_handler():
    """Handle unauthorized requests."""
    return Response(json.dumps({
        'code': 'unauthorized',
        'message': "Unauthorized."
    }, ensure_ascii=True), status=401, content_type="application/json")

If you want to change this behavior, you can modify the ensure_ascii parameter to False in the relevant parts of the code where JSON serialization occurs [1].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Jul 24, 2024): <!-- Answer --> The tool information in the prompt is in ASCII encoding format because the `ensure_ascii` parameter is set to `True` in the JSON serialization process. This is not an error but a deliberate setting in the codebase. For example, in the `unauthorized_handler` function, the `json.dumps` method is used with `ensure_ascii=True`: ```python @login_manager.unauthorized_handler def unauthorized_handler(): """Handle unauthorized requests.""" return Response(json.dumps({ 'code': 'unauthorized', 'message': "Unauthorized." }, ensure_ascii=True), status=401, content_type="application/json") ``` If you want to change this behavior, you can modify the `ensure_ascii` parameter to `False` in the relevant parts of the code where JSON serialization occurs <sup>[[1]](https://github.com/langgenius/dify/blob/main/api/app.py)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:07:55 -05:00
Author
Owner
Copy Link
Copy Source

@401557122 commented on GitHub (Jul 24, 2024):

@dosu What is the purpose of setting this

@401557122 commented on GitHub (Jul 24, 2024): @dosu What is the purpose of setting this
yindo commented 2026-02-21 18:07:55 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jul 24, 2024):

Setting ensure_ascii=True in the JSON serialization process ensures that the output is ASCII-only by escaping all non-ASCII characters using \uXXXX sequences. This can be useful for compatibility with systems that may not handle non-ASCII characters properly.

Changing ensure_ascii to False allows the JSON encoder to output non-ASCII characters as-is, making the JSON data more readable and compact if it contains many non-ASCII characters.

Example:

import json

data = {"message": "Hola, ¿cómo estás?"}

# ensure_ascii=True
json_data_ascii = json.dumps(data, ensure_ascii=True)
print(json_data_ascii)  # Output: {"message": "Hola, \u00bfcómo est\u00e1s?"}

# ensure_ascii=False
json_data_non_ascii = json.dumps(data, ensure_ascii=False)
print(json_data_non_ascii)  # Output: {"message": "Hola, ¿cómo estás?"}

In the first case, non-ASCII characters are escaped, while in the second case, they are preserved [1].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Jul 24, 2024): <!-- Answer --> Setting `ensure_ascii=True` in the JSON serialization process ensures that the output is ASCII-only by escaping all non-ASCII characters using `\uXXXX` sequences. This can be useful for compatibility with systems that may not handle non-ASCII characters properly. Changing `ensure_ascii` to `False` allows the JSON encoder to output non-ASCII characters as-is, making the JSON data more readable and compact if it contains many non-ASCII characters. Example: ```python import json data = {"message": "Hola, ¿cómo estás?"} # ensure_ascii=True json_data_ascii = json.dumps(data, ensure_ascii=True) print(json_data_ascii) # Output: {"message": "Hola, \u00bfcómo est\u00e1s?"} # ensure_ascii=False json_data_non_ascii = json.dumps(data, ensure_ascii=False) print(json_data_non_ascii) # Output: {"message": "Hola, ¿cómo estás?"} ``` In the first case, non-ASCII characters are escaped, while in the second case, they are preserved <sup>[[1]](https://github.com/langgenius/dify/blob/main/web/public/vs/editor/editor.main.nls.es.js)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:07:55 -05:00
Author
Owner
Copy Link
Copy Source

@401557122 commented on GitHub (Jul 24, 2024):

But the prompts are all Ascii encoded, can LLMs understand @dosu

@401557122 commented on GitHub (Jul 24, 2024): But the prompts are all Ascii encoded, can LLMs understand @dosu
yindo commented 2026-02-21 18:07:55 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jul 24, 2024):

LLMs (Large Language Models) can understand prompts encoded in ASCII as well as those containing non-ASCII characters. However, encoding prompts in ASCII (using \uXXXX sequences for non-ASCII characters) can make the text less readable for humans but does not affect the model's ability to process the information.

If readability is a concern and you want to ensure that non-ASCII characters are preserved in their original form, you can modify the ensure_ascii parameter to False in the JSON serialization process. This will allow the JSON encoder to output non-ASCII characters as-is, making the prompts more readable.

For example, in the unauthorized_handler function, you can change:

return Response(json.dumps({
    'code': 'unauthorized',
    'message': "Unauthorized."
}, ensure_ascii=True), status=401, content_type="application/json")

to:

return Response(json.dumps({
    'code': 'unauthorized',
    'message': "Unauthorized."
}, ensure_ascii=False), status=401, content_type="application/json")

This change will preserve non-ASCII characters in their original form in the JSON output.

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Jul 24, 2024): <!-- Answer --> LLMs (Large Language Models) can understand prompts encoded in ASCII as well as those containing non-ASCII characters. However, encoding prompts in ASCII (using `\uXXXX` sequences for non-ASCII characters) can make the text less readable for humans but does not affect the model's ability to process the information. If readability is a concern and you want to ensure that non-ASCII characters are preserved in their original form, you can modify the `ensure_ascii` parameter to `False` in the JSON serialization process. This will allow the JSON encoder to output non-ASCII characters as-is, making the prompts more readable. For example, in the `unauthorized_handler` function, you can change: ```python return Response(json.dumps({ 'code': 'unauthorized', 'message': "Unauthorized." }, ensure_ascii=True), status=401, content_type="application/json") ``` to: ```python return Response(json.dumps({ 'code': 'unauthorized', 'message': "Unauthorized." }, ensure_ascii=False), status=401, content_type="application/json") ``` This change will preserve non-ASCII characters in their original form in the JSON output. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label stale 📚 documentation
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#4762
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?