From: "jgart" <jgart@dismail.de>
To: "Arun Isaac" <arunisaac@systemreboot.net>, kaagum@systemreboot.net
Subject: Re: [PATCH] Remove #:streaming? #t from HTTP requests to fix JSON parsing
Date: Tue, 21 Jul 2026 08:51:43 +0000 [thread overview]
Message-ID: <0e258653bf3bb4c5dbae700ffd6119153b523a91@dismail.de> (raw)
In-Reply-To: <87zezlgqrj.fsf@systemreboot.net>
Hi Arun,
Sorry about this. I used a DeepSeek model in the pi agent harness to work on the patch and description, and it looks like it hallucinated the technical details. The claim about gzip/streaming causing invalid JSON, and the openai-models workaround with accept-encoding: identity, don't seem to be real.
Looking back at what I actually have, the closest thing to evidence is an error like this I took from an earlier screenshot when I captured the error:
(error (code . -32603)
(message . "Agent process ended before completing request: exited abnormally with code 1"))
This looks like a crashed subprocess, not a JSON parsing issue.
The model I configured kaagum with was anthropic/claude-sonnet-4.6 as mentioned in the README.
I used OpenRouter and fed kaagum my OpenRouter API key via the pass CLI flag example as mentioned in the example section in the README.
I'll look into the actual subprocess crash and get back to you with something concrete when I can reproduce it.
Apologies for the noise.
Thanks,
jgart
next prev parent reply other threads:[~2026-07-21 8:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 14:21 jgart
2026-07-20 14:21 ` [PATCH] Remove #:streaming? #t from HTTP requests jgart
2026-07-20 23:55 ` [PATCH] Remove #:streaming? #t from HTTP requests to fix JSON parsing Arun Isaac
2026-07-21 8:51 ` jgart [this message]
2026-07-21 23:43 ` Arun Isaac
2026-07-22 3:31 ` jgart
2026-07-22 11:03 ` Arun Isaac
2026-08-14 11:52 ` jgart
2026-08-14 13:01 ` Arun Isaac
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0e258653bf3bb4c5dbae700ffd6119153b523a91@dismail.de \
--to=jgart@dismail.de \
--cc=arunisaac@systemreboot.net \
--cc=kaagum@systemreboot.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox