-
Notifications
You must be signed in to change notification settings - Fork 229
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
In many applications, output.text is too long to input #35
Comments
|
It might also be possible to apply a soft form of minification, that cuts and removes more fat, preserves just enough structure and meaning for GPT4 to still understand (e.g. removing all whitespaces, some vowels, many non-critical words in comments (e.g. a, to, the...) etc. I wouldn't be surprised if there wasn't already such an algorithm somewhere. |
[UPDATE]: I just realized this feature already exists on this repository with here's mine:
|
Thank you for the wonderful tool!
Problem
When inputting to GPT-4 at once, I get the error "The message you submitted was too long, please reload the conversation and submit something shorter."
Details
In my fairly simple React app, when I output output.text, the number of lines reached 6 million, and of course, most of it was node_modules. When I excluded descriptions unrelated to the app, such as node_modules, yarn.lock, and .git/, it reduced to about 1,500 lines, but I still got the same error.
Now, I've declared to send one file at a time, and by repeatedly copying and pasting, it seems that the files can be read.
Suggestion
It might be useful to have features like the following:
By the way
With GPT-4, I could send about 400 lines at a time (4-5 files).
Also, every time I sent it, the contents of the file were properly explained, and when I sent it up to --END--, it even created a summary for me, which was impressive.
From now on, I would like to verify whether GPT can handle code maintenance and adding new features.
The text was updated successfully, but these errors were encountered: