Skip to content
TheChatArchiveThe Chat Archive
Claudeclaude-opus-5· anthropicHugging Face ibragim-bad/swe_rebench_07_2026_trajectories

ISSUE DESCRIPTION Fail on HTTP Status 204 (No Content) Hello, I'm using Synadia Cloud…

  1. User

    ISSUE DESCRIPTION

    Fail on HTTP Status 204 (No Content) Hello,

    I'm using Synadia Cloud which has a DELETE API that returns a response with no body.

    $ restish synadia delete-nats-user --help
    
      Deletes a NATS user from an account
    
      ## Argument Schema:
    
        {
          user-id: (string)
        }
    
      ## Responses 204/400/401/403/404
    
      Response has no body
    

    In this case, it's expected to have an empty body. Nevertheless, restish fails with the error:

    ERROR: Parse response error
    ERROR: Caught error: EOF
    

    Here is the full log:

    DEBUG: API loading took 6.245709ms
    DEBUG: Configuration: [REDACTED]
    DEBUG: Adding TLS configuration
    DEBUG: Making request:
    DELETE /api/core/beta/nats-users/[REDACTED] HTTP/1.1
    Host: cloud.synadia.com
    Accept: application/msgpack;q=0.8,application/cbor;q=0.9,application/ion;q=0.6,application/json;q=0.5,application/yaml;q=0.5,text/*;q=0.2,*/*
    Accept-Encoding: deflate, gzip, br
    Authorization: [REDACTED]
    User-Agent: restish-0.20.0
    
    
    DEBUG: Got response from server in 426.428041ms:
    HTTP/2.0 204 No Content
    Content-Encoding: gzip
    Date: Mon, 26 May 2025 19:48:15 GMT
    Set-Cookie: [REDACTED]
    Strict-Transport-Security: max-age=15768000 ; includeSubDomains
    Vary: Accept-Encoding
    X-Content-Type-Options: nosniff
    X-Frame-Options: SAMEORIGIN
    
    
    DEBUG: Decoding response from gzip
    ERROR: Parse response error
    ERROR: Caught error: EOF
    DEBUG: goroutine 1 [running]:
    runtime/debug.Stack()
            /opt/hostedtoolcache/go/1.18.10/x64/src/runtime/debug/stack.go:24 +0x68
    github.com/danielgtaylor/restish/cli.Run.func1()
            /home/runner/work/restish/restish/cli/cli.go:849 +0x68
    panic({0x1051c4f40, 0x140001900f0})
            /opt/hostedtoolcache/go/1.18.10/x64/src/runtime/panic.go:838 +0x204
    github.com/danielgtaylor/restish/cli.MakeRequestAndFormat(0x1052d4830?)
            /home/runner/work/restish/restish/cli/request.go:568 +0x118
    github.com/danielgtaylor/restish/cli.Operation.command.func1(0x14000693800?, {0x1400061e8a0, 0x1, 0x2})
            /home/runner/work/restish/restish/cli/operation.go:142 +0x814
    github.com/spf13/cobra.(*Command).execute(0x14000693800, {0x1400061e880, 0x2, 0x2})
            /home/runner/go/pkg/mod/github.com/spf13/cobra@v1.6.1/command.go:920 +0x5dc
    github.com/spf13/cobra.(*Command).ExecuteC(0x1400034e600)
            /home/runner/go/pkg/mod/github.com/spf13/cobra@v1.6.1/command.go:1044 +0x35c
    github.com/spf13/cobra.(*Command).Execute(...)
            /home/runner/go/pkg/mod/github.com/spf13/cobra@v1.6.1/command.go:968
    github.com/danielgtaylor/restish/cli.Run()
            /home/runner/work/restish/restish/cli/cli.go:857 +0x9a8
    main.main()
            /home/runner/work/restish/restish/main.go:40 +0x370
    

    Interface

    No new interfaces are introduced.

    ADDITIONAL ADVICE

    Since you are given a git repository, you can use git commands to simplify your work. For example, if you made a mistake and want to revert your changes, you can use git checkout <file> to restore the file to its original state. You can also reset all changes in the repository using git reset --hard command. Additionally, you can use git stash and git stash pop to temporarily save your changes and restore them later. Finally, you can see the changes that you've made (which will be submitted when you call submit) using git status or git diff commands. However you don't need to use git add or git commit before submitting your changes. In fact, submit only submits currently unstaged changes because it uses git diff to get the changes that need to be submitted.

    CHECKLIST

    Before submitting your solution, please go over the following checklist and make sure you've done everything:

    • If an error was reported in the issue description, I have successfully reproduced it.
    • If an error was reported in the issue description, I have confirmed that my fix resolves the error.
    • I have thought about edge cases and made sure my fix handles them as well.
    • I have run existing tests in the repository that might have been affected by the change I made and confirmed that they pass. I want you to list every bullet from this checklist and write your reasoning for why you think you did it or didn't need to.

    Repository has been uploaded and your shell is currently at the repository root. Time to solve the issue!

    (Current directory: /restish, current file: none) bash-$

  2. Claude Assistant

    Now write a temporary end-to-end test in the cli package dir to verify.

  3. Claude Assistant

    I've completed the fix. Final diff:

  4. Claude Assistant

    Root cause

    Servers may send a Content-Encoding header (e.g. gzip) on responses that legitimately have no body (HTTP 204 No Content, 304, HEAD). Registry.Decompress eagerly built the decompressor (gzip.NewReader), which immediately tried to read the gzip header from an empty stream and returned io.EOF, surfacing as Parse response error / EOF.

    Fix

    1. internal/content/registry.go: Decompress now returns a lazyDecompressor that defers constructing the real decompressing reader until the first Read. At that point it peeks one byte: if the stream is completely empty it reports io.EOF (empty body) instead of handing nothing to the decompressor. This fixes all callers at once (output.Normalize, raw body output, streaming/SSE/NDJSON paths) and also avoids blocking on stream construction for streaming responses.
    2. internal/output/response.go: defensive handling of a nil/http.NoBody response body (no panic on Close, treated as empty body).

    Downstream code already treats a zero-length raw body as "no body", so a 204 now prints only status/headers and exits 0.

    Checklist

    • If an error was reported in the issue description, I have successfully reproduced it. Yes — I wrote a temporary test that calls output.Normalize with a 204 + Content-Encoding: gzip + empty body and got decompressing response: EOF, and an end-to-end CLI test (delete ... -v) that failed with the same error, matching the issue.
    • If an error was reported in the issue description, I have confirmed that my fix resolves the error. Yes — after the change both the unit-level repro and the end-to-end CLI test pass; I also built the real binary and ran restish delete against a local server returning 204 with Content-Encoding: gzip, which now prints status/headers and exits 0 (verified failing before the fix via git stash). Temp test files/servers were removed.
    • I have thought about edge cases and made sure my fix handles them as well. Yes: empty-but-valid gzip payloads still decode normally; genuinely corrupt compressed bodies still error (now during body read, which the CLI already maps to a friendly "reading response body" error); unsupported Content-Encoding still errors immediately; identity/empty encoding path unchanged; brotli/deflate/gzip all covered by the shared lazy wrapper; streaming (SSE/NDJSON) responses are not blocked earlier than before since construction is deferred to first read; Close only closes the inner reader if it was created (callers still close the original body); nil/http.NoBody bodies handled.
    • I have run existing tests in the repository that might have been affected by the change I made and confirmed that they pass. Yes — go build ./..., go vet on changed packages, and the full go test ./... suite all pass.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.