-
Notifications
You must be signed in to change notification settings - Fork 761
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
JSON generation failures #201
Comments
Hey @benbot, sorry that you ran into issues! Were you using the default models? That error message (will be improved in the next release) means that the LLM couldn't generate valid json. This shouldn't ever be happening these days with OpenAI models so it's definitely a bit strange to see if you're using the defaults. I'm not familiar with nix (the package was added by a contributor) so I'm not sure how to check whether you're getting the latest version there. Perhaps that could be a factor. |
@danenania I tried with both the default models and claude sonnet. I took a peek into the nix package definition and it seems to be running version 1.1.1 |
@notatestuser @benbot Sonnet tends to have a lot of JSON generation issues unfortunately. I'd recommend trying the @benbot Ok, sounds like the nix version is fine then. If you start fresh with either the |
it doesn't happen for me with |
I believe i'm on the development brach as
plandex version
says "development", but I got plandex through nixpkgs.I'm trying to test out plandex by having it generate some tests for an elixir project i'm working on.
First I tried to
plandex tell
it to generate some missing tests, it froze during this process 2/3 times.When it froze, the only way I knew that it erroed was the status message in
plandex ps
. It gave me no other indication that an error occurred, the generation just froze and appeared to keep spinning. I still don't know what the exact error was.Afterwards, it seemed to complete its changes, but
plandex apply
always results inSo after an hour and 30 cents, I'm giving up on plandex for now.
Maybe it doesn't like elixir very much, but it's hard for me to tell as these error messages give me nothing to work with and it's not clear how to view the intermediate prompts.
The text was updated successfully, but these errors were encountered: