-
Notifications
You must be signed in to change notification settings - Fork 558
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
The reply result will be truncated #352
Labels
bug
Something isn't working
Comments
Same problem here. I guess this limit comes from GPT... |
Same problem, hope you guys fix it as soon as possible. Bloop helped me write really nice codes, I love it. |
Currently, a solution has been found: by inputting "continue", the internal GPT can continue to return results. Although this may have some impact on answering a question, "continue" is also understandable from an interactive perspective. |
Thank you so much!!!
| |
余范锝
|
|
***@***.***
|
---- Replied Message ----
| From | ***@***.***> |
| Date | 4/24/2023 23:14 |
| To | ***@***.***> |
| Cc | Yu ***@***.***> ,
***@***.***> |
| Subject | Re: [BloopAI/bloop] The reply result will be truncated (Issue #352) |
Currently, a solution has been found: by inputting "continue", the internal GPT can continue to return results. Although this may have some impact on answering a question, "continue" is also understandable from an interactive perspective.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When I ask about the execution process of a function in a certain file, if the reply is too long, it may be truncated.
Expected behavior
Screenshots or output
![image](https://user-images.githubusercontent.com/29874640/228493957-a459fc84-76dd-4e81-b241-69b6432ec01a.png)
![image](https://user-images.githubusercontent.com/29874640/228493884-1902c137-284f-4419-89ef-612243a0ceae.png)
The text was updated successfully, but these errors were encountered: