fix preprocess_fncall_messages #660
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fix the preprocess_fncall_maessages function to address the issue of escape character errors in messages
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fix the preprocess_fncall_maessages function to address the issue of escape character errors in messages.
针对issue中提出的 NousFnCallPrompt 类的 preprocess_fncall_messages 函数会错误地构造 messages 的问题，解决了二次转义带来的错误，防止 preprocess_fncall_messages 对输入 functions 作出的错误修改，将 json 字符串化之后的 tool_descs 进行反向转义解码，使输出 messages 与函数输入保持一致。