修复了maxtoken逻辑问题 - #11
Merged
Merged
Conversation
Contributor
Author
|
貌似遇到了构建镜像的权限问题，但我提交pr貌似没权限也合理吧，不知道是不是我操作有什么问题，第一次用这种github action推镜像的，还麻烦佬指点一下 |
Collaborator
|
merge了，之前是别人没有推送镜像的权限但仍然进行了构建尝试，现在删除了PR时构建触发 |
Collaborator
|
自己推送的话在自己的repo里开启workflow就可以了，推送到自己的ghcr.io仓库上 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
原逻辑为：总输出文本达到65535时截断
改为：总输出文本达到maxtoken时截断，客户端没输入就默认65535