JSON output is not JSON

Open Beginner friendly
#70 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Reproduce the issue with sush job output <job> -j and trace the command's JSON output path. The fix is done when the output is valid JSON for multiple targets, with the target and stdout represented in one parseable document.

Written by the indexing model from the issue text.

Description

alan@castle:~$ /staff/alex/sush job output off-because-about-tide-detail-fruit-empty-forward
 » 913-0000019:BRM23230010 «
✅ Job stdout:
21:53:11    up 3 day(s), 22:17,  0 users,  load average: 1.45, 1.54, 1.72
 » 913-0000019:BRM23230018 «
✅ Job stdout:
21:53:11    up 3 day(s), 22:16,  0 users,  load average: 2.75, 3.05, 3.22
 » 913-0000019:BRM27230037 «
✅ Job stdout:
21:53:11    up 3 day(s), 22:15,  0 users,  load average: 1.13, 1.36, 1.63
 » 913-0000023:2F8JEXDK «
✅ Job stdout:
21:53:10    up 2 day(s), 46 min(s),  0 users,  load average: 1.76, 2.10, 2.35
alan@castle:~$ /staff/alex/sush job output off-because-about-tide-detail-fruit-empty-forward -j
{"target":"913-0000019:BRM23230010"}
"21:53:11    up 3 day(s), 22:17,  0 users,  load average: 1.45, 1.54, 1.72\n"
{"target":"913-0000019:BRM23230018"}
"21:53:11    up 3 day(s), 22:16,  0 users,  load average: 2.75, 3.05, 3.22\n"
{"target":"913-0000019:BRM27230037"}
"21:53:11    up 3 day(s), 22:15,  0 users,  load average: 1.13, 1.36, 1.63\n"
{"target":"913-0000023:2F8JEXDK"}
"21:53:10    up 2 day(s), 46 min(s),  0 users,  load average: 1.76, 2.10, 2.35\n"
Dominant language
Rust
Stars
3
Forks
0
Avg merge
9d 12h
Merged PRs (30d)
11

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.

More from oxidecomputer/sush

All issues in oxidecomputer/sush

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.