karthink
karthink
This error is different from the one in your previous post. It looks like there are two different errors. Please turn off logging with `(setq gptel-log-level nil)` and produce a...
That's quite odd. I'd ask you to turn on logging but that's independently broken too. I don't see anything wrong with that `json-serialize` call.
No, I think it's related to `string-trim` further below. To analyze this I'd have to fix the logging bug first.
I'm hoping PR #456 has solved this issue. If you have/had this problem, could you test it with the latest gptel commit?
Cool, please reopen if this issue persists.
Ah yeah, I'm aware of this issue. It's unrelated to Org mode. See prior discussions in #406, #321, #351, #343. There is no easy fix for this yet. Rather, there...
@agzam, @wlauppe could you try it now? I added a clause to the logic for Anthropic where I don't include "empty" user prompts in the message. (Even if this works,...
Closing this now. @wlauppe and @agzam, feel free to reopen if you can still reproduce the error.
> karthik, if you write an updated `:GPTEL_BOUNDS: ` line, do you account for the changes in length? For example if it had length 10 and the new `:GPTEL_BOUNDS: `...
> and this workaround obscures the fact that something is broken. If you are referring to the workaround chosen as the solution in this thread, it's a workaround, but nothing...