修复api接口websocket的伪流式输出 #628
Merged
Conversation
This file contains 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
修复websocket的伪流式输出
|
太棒了 搞了两天 才发现是这里的问题 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
不清楚是不是因为websocket的问题。
在使用postman连接ws接口时，虽然发送的信息还是流式的，但是并不实时，获取推理结果时会最后一起拿到几十条。
因此在流式推理结果send前添加sleep，类似于nextTick这样的操作，使得推理结果会实时返回，达到真流式输出的结果。
修复后，经测试，postman可以顺畅的实时接受流式结果。