You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The error Malformed response #2, retrying...
InvalidEditBlock: edit failed!
does not contain the exact sequence of HEAD lines you specified.
Try again.
DO NOT skip blank lines, comments, docstrings, etc!
The HEAD block needs to be EXACTLY the same as the lines in assets/js/output.js with nothing missing!
does not contain these 2 exact lines in a row:
// Step 1: `
Issue: The error causes a loop where aider keeps trying to fix the issue with updating the file. This burns through tokens fast and is incredibly expensive as it keep generating the same old code, then the new code updates, etc. If it does not catch the issue on the second go around, it will keep trying.
The text was updated successfully, but these errors were encountered:
generallynonsensical
changed the title
Adding "Step" comments cause error loops
GPT Adding Comments Cause Errors When Updating Files
Aug 31, 2023
Unfortunately even GPT-4 gets confused sometimes. You can always safely halt it by hitting CONTROL-C and then tell it to stop doing whatever it's doing wrong.
Another thing to try is to add fewer files to the chat, so GPT can focus more on the specific files you want it to change.
Usage: aider via terminal in vscode, debian
Error:
The error
Malformed response #2, retrying...InvalidEditBlock: edit failed!
does not contain the exact sequence of HEAD lines you specified.
Try again.
DO NOT skip blank lines, comments, docstrings, etc!
The HEAD block needs to be EXACTLY the same as the lines in assets/js/output.js with nothing missing!
does not contain these 2 exact lines in a row:
// Step 1: `
Issue: The error causes a loop where aider keeps trying to fix the issue with updating the file. This burns through tokens fast and is incredibly expensive as it keep generating the same old code, then the new code updates, etc. If it does not catch the issue on the second go around, it will keep trying.
The text was updated successfully, but these errors were encountered: