hciconfig

--hciconfigv1.4.0

`hciconfig` command parser

Linuxcommand

$ hciconfig | jc-rs --hciconfig

A real pair

From the reference corpus (centos-7.7/hciconfig.json). The left pane is the input the fixture ships; the right pane is the corpus's expected JSON. CI compares jc-rs with it field by field under the published differential. Hover a value to see where it came from.

hciconfigcentos-7.7

hci0:   Type: Primary  Bus: USB
    BD Address: 00:50:56:FE:FD:38  ACL MTU: 8192:128  SCO MTU: 64:128
    DOWN 
    RX bytes:503 acl:0 sco:0 events:22 errors:0
    TX bytes:336 acl:0 sco:0 commands:22 errors:0

expected outputjson

[
  {
    "device": "hci0",
    "type": "Primary",
    "bus": "USB",
    "bd_address": "00:50:56:FE:FD:38",
    "acl_mtu": 8192,
    "acl_mtu_packets": 128,
    "sco_mtu": 64,
    "sco_mtu_packets": 128,
    "state": [
      "DOWN"
    ],
    "rx_bytes": 503,
    "rx_acl": 0,
    "rx_sco": 0,
    "rx_events": 22,
    "rx_errors": 0,
    "tx_bytes": 336,
    "tx_acl": 0,
    "tx_sco": 0,
    "tx_commands": 22,
    "tx_errors": 0
  }
]

Fixture coverage

4/4oracle-valid pairs match under the published structural JSON comparison

Magic syntax

jc-rs hciconfigjc-rs runs the command itself and parses what it prints. Recognised for: `hciconfig`

Source: crates/jc-rs-parsers/src/misc/hciconfig.rs. jc-rs targets the schemas defined by the original Python tool. Fixture coverage above is the measured evidence for this parser; test the inputs your pipeline depends on. Compare