ss: stdout differs from oracle for ss -s

Open
#275 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
go, linux

Research direction

Locate the ss builtin and its handling of the -s option, then reproduce ss -s and compare its stdout with the oracle output in this issue. Done means the command exits 0, emits the expected summary format and values, and keeps stderr empty.

Written by the indexing model from the issue text.

Description

QA

Summary

rshell and the oracle produced different results for ss -s.

Command

ss -s

Reduced command shape: ss -s

Expected (oracle)

Exit code: 0

stdout:

Total: 305
TCP:   373 (estab 137, closed 223, orphaned 0, timewait 136)

Transport Total     IP        IPv6
RAW	  0         0         0        
UDP	  1         1         0        
TCP	  150       135       15       
INET	  151       136       15       
FRAG	  0         0         0        

stderr:

(empty)

Actual (rshell)

Exit code: 0

stdout:

Total: 430
TCP:   286 (ipv4: 267, ipv6: 19)
UDP:   1 (ipv4: 1, ipv6: 0)
Unix:  143

stderr:

(empty)

Why This Matters

The QA run observed this command shape in 43 invocations across 42 scenarios.

Additional Observed Command Shapes

  • ss -s && ss -tanH | grep "10.244.0.77:9092\|10.96.59.83:9092" | head -n 20
QA provenance
  • QA run id: run-20260602t141945z-ss
  • Target builtin: ss
  • Rshell commit/version: unknown
  • Example invocation: inv-20260602T143111.282399142Z-66f1c389
  • Observed invocations: 43
  • Scenario count: 42
  • Differing dimension: stdout
Dominant language
Go
Stars
31
Forks
3
Avg merge
1d 12h
Merged PRs (30d)
11

Contributor guide

Open the contributing guide

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 DataDog/rshell

All issues in DataDog/rshell

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.