Skip to content

error passing? #2

@mitchcapper

Description

@mitchcapper

I am not sure if aider would handle errors well or not, but trying to review its error code it looks like it may not be getting errors in the form expected from copilot proxy.

Was trying to use aider to improve aider ( Aider-AI/aider#3210 ) which involved asking it to edit gui.py. That is ~18KB file. While I tried to keep aider in diff mode it still would seem to like to request full files if I approved it adding changes to gui.py most of the time. This with claude for example would almost always result in copilot proxy throwing an error about too large of a response. This error didn't seem to actually get back to aider though, so aider would just hang and have to be force killed and restarted (and then try to avoid the landmine of it requesting the full gui.py file again).

I do see the error in the VS output window, but not sure if it should be massaged into more of the LiteLLMExceptions format that aider expects?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions