oxidecomputer / oxidecomputer/rfd-api

`rfd-cli discussion` command appears to always fail with an unexpected EOF

Open
#526 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
95
Forks
22
Avg merge
6d 19h
Merged PRs (30d)
17

Description

For example:

eliza@theseus ~ $ rfd-cli version
0.15.5 (11c64bb0b50eb5b82911851223eb6d9809e85839, dev)

eliza@theseus ~ $ rfd-cli discussion --number 699
Invalid Response Payload (b""): EOF while parsing a value at line 1 column 0

eliza@theseus ~ $ rfd-cli discussion --number 603
Invalid Response Payload (b""): EOF while parsing a value at line 1 column 0

eliza@theseus ~ $ rfd-cli discussion --number 520
Invalid Response Payload (b""): EOF while parsing a value at line 1 column 0

eliza@theseus ~ $ rfd-cli discussion --number 704
Invalid Response Payload (b""): EOF while parsing a value at line 1 column 0

eliza@theseus ~ $ rfd-cli discussion --number 1
Invalid Response Payload (b""): EOF while parsing a value at line 1 column 0

eliza@theseus ~ $ 

This seems to happen pretty consistently with every RFD. rfd-cli list and rfd-cli view do not fail like this.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing rfd-cli discussion --number 699 and compare its request and response handling with rfd-cli list and rfd-cli view. Trace the rfd-cli discussion entry point to identify why valid RFDs produce an empty response and EOF parsing error. Done means the discussion command returns discussion data successfully for RFD numbers such as 699, 603, 520, 704, and 1.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.