Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

error parsing OID Value: invalid OID length #387

Open
cemremengu opened this issue Dec 16, 2021 · 7 comments
Open

error parsing OID Value: invalid OID length #387

cemremengu opened this issue Dec 16, 2021 · 7 comments

Comments

@cemremengu
Copy link
Contributor

cemremengu commented Dec 16, 2021 •
edited
Loading

I am using BulkWalkAll successfully for all devices to read IF-MIB. However for 1 particular device (which is same in every aspect with other devices), I am getting he error error parsing OID Value: invalid OID length. I can see that the values are returned over the wire but not sure where it goes wrong. Maybe one package is big and is not fragmented correctly?

Below is the tcp dump. Any ideas why this might be happening?

tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
12:52:57.831570 IP (tos 0x0, ttl 63, id 13315, offset 0, flags [DF], proto UDP (17), length 81)
    mysnmphost.47247 > 10.0.232.216.snmp: [bad udp cksum 0x8eca -> 0x0ee6!]  { SNMPv2c C="SnmP_" { GetRequest(28) R=1217588377  system.sysObjectID.0 } }
12:52:57.896302 IP (tos 0x0, ttl 249, id 62508, offset 0, flags [none], proto UDP (17), length 93)
    10.0.232.216.snmp > mysnmphost.47247: [udp sum ok]  { SNMPv2c C="SnmP_" { GetResponse(40) R=1217588377  system.sysObjectID.0=E:2011.2.224.132 } }
12:52:57.896584 IP (tos 0x0, ttl 63, id 13346, offset 0, flags [DF], proto UDP (17), length 83)
    mysnmphost.47247 > 10.0.232.216.snmp: [bad udp cksum 0x8ecc -> 0xb3da!]  { SNMPv2c C="SnmP_" { GetBulk(30) R=1217588378  N=0 M=50 31.1.1.1.1 } }
12:52:58.151051 IP (tos 0x0, ttl 249, id 62509, offset 0, flags [none], proto UDP (17), length 1140)
    10.0.232.216.snmp > mysnmphost.47247: [udp sum ok]  { SNMPv2c C="SnmP_" { GetResponse(1083) R=1217588378  31.1.1.1.1.1="InLoopBack0" 31.1.1.1.1.2="NULL0" 31.1.1.1.1.3="GigabitEthernet0/0/0" 31.1.1.1.1.4="GigabitEthernet0/0/1" 31.1.1.1.1.5="GigabitEthernet0/0/2" 31.1.1.1.1.6="GigabitEthernet0/0/3" 31.1.1.1.1.7="GigabitEthernet0/0/4" 31.1.1.1.1.8="Cellular0/0/0" 31.1.1.1.1.9="Vlanif1" 31.1.1.1.1.10="GigabitEthernet0/0/4.500" 31.1.1.1.1.11="LoopBack0" 31.1.1.1.2.1=0 31.1.1.1.2.2=0 31.1.1.1.2.3=1033337 31.1.1.1.2.4=0 31.1.1.1.2.5=0 31.1.1.1.2.6=0 31.1.1.1.2.7=37718 31.1.1.1.2.8=0 31.1.1.1.2.9=0 31.1.1.1.2.10=0 31.1.1.1.2.11=0 31.1.1.1.3.1=0 31.1.1.1.3.2=0 31.1.1.1.3.3=1255240 31.1.1.1.3.4=0 31.1.1.1.3.5=0 31.1.1.1.3.6=0 31.1.1.1.3.7=3 31.1.1.1.3.8=0 31.1.1.1.3.9=0 31.1.1.1.3.10=3 31.1.1.1.3.11=0 31.1.1.1.4.1=0 31.1.1.1.4.2=0 31.1.1.1.4.3=276 31.1.1.1.4.4=0 31.1.1.1.4.5=0 31.1.1.1.4.6=0 31.1.1.1.4.7=0 31.1.1.1.4.8=0 31.1.1.1.4.9=0 31.1.1.1.4.10=0 31.1.1.1.4.11=0 31.1.1.1.5.1=0 31.1.1.1.5.2=0 31.1.1.1.5.3=111826 31.1.1.1.5.4=0 31.1.1.1.5.5=0 31.1.1.1.5.6=0 } }
12:52:58.151372 IP (tos 0x0, ttl 63, id 13583, offset 0, flags [DF], proto UDP (17), length 82)
    mysnmphost.47247 > 10.0.232.216.snmp: [bad udp cksum 0x8ecb -> 0xcfe0!]  { SNMPv2c C="SnmP_" { GetBulk(29) R=1217588379  N=0 M=50 interfaces.ifTable.ifEntry.ifDescr } }
12:52:58.405949 IP (tos 0x0, ttl 249, id 62510, offset 0, flags [none], proto UDP (17), length 1148)
    10.0.232.216.snmp > mysnmphost.47247: [udp sum ok]  { SNMPv2c C="SnmP_" { GetResponse(1091) R=1217588379  interfaces.ifTable.ifEntry.ifDescr.1="InLoopBack0" interfaces.ifTable.ifEntry.ifDescr.2="NULL0" interfaces.ifTable.ifEntry.ifDescr.3="GigabitEthernet0/0/0" interfaces.ifTable.ifEntry.ifDescr.4="GigabitEthernet0/0/1" interfaces.ifTable.ifEntry.ifDescr.5="GigabitEthernet0/0/2" interfaces.ifTable.ifEntry.ifDescr.6="GigabitEthernet0/0/3" interfaces.ifTable.ifEntry.ifDescr.7="GigabitEthernet0/0/4" interfaces.ifTable.ifEntry.ifDescr.8="Cellular0/0/0" interfaces.ifTable.ifEntry.ifDescr.9="Vlanif1" interfaces.ifTable.ifEntry.ifDescr.10="GigabitEthernet0/0/4.500" interfaces.ifTable.ifEntry.ifDescr.11="LoopBack0" interfaces.ifTable.ifEntry.ifType.1=24 interfaces.ifTable.ifEntry.ifType.2=1 interfaces.ifTable.ifEntry.ifType.3=6 interfaces.ifTable.ifEntry.ifType.4=6 interfaces.ifTable.ifEntry.ifType.5=6 interfaces.ifTable.ifEntry.ifType.6=6 interfaces.ifTable.ifEntry.ifType.7=6 interfaces.ifTable.ifEntry.ifType.8=160 interfaces.ifTable.ifEntry.ifType.9=53 interfaces.ifTable.ifEntry.ifType.10=135 interfaces.ifTable.ifEntry.ifType.11=24 interfaces.ifTable.ifEntry.ifMtu.1=1500 interfaces.ifTable.ifEntry.ifMtu.2=1500 interfaces.ifTable.ifEntry.ifMtu.3=2048 interfaces.ifTable.ifEntry.ifMtu.4=2048 interfaces.ifTable.ifEntry.ifMtu.5=2048 interfaces.ifTable.ifEntry.ifMtu.6=2048 interfaces.ifTable.ifEntry.ifMtu.7=1500 interfaces.ifTable.ifEntry.ifMtu.8=1500 interfaces.ifTable.ifEntry.ifMtu.9=1500 interfaces.ifTable.ifEntry.ifMtu.10=1500 interfaces.ifTable.ifEntry.ifMtu.11=1500 interfaces.ifTable.ifEntry.ifSpeed.1=0 interfaces.ifTable.ifEntry.ifSpeed.2=0 interfaces.ifTable.ifEntry.ifSpeed.3=1000000000 interfaces.ifTable.ifEntry.ifSpeed.4=1000000000 interfaces.ifTable.ifEntry.ifSpeed.5=1000000000 interfaces.ifTable.ifEntry.ifSpeed.6=1000000000 interfaces.ifTable.ifEntry.ifSpeed.7=1000000000 interfaces.ifTable.ifEntry.ifSpeed.8=10000000 interfaces.ifTable.ifEntry.ifSpeed.9=1000000000 interfaces.ifTable.ifEntry.ifSpeed.10=1000000000 interfaces.ifTable.ifEntry.ifSpeed.11=0 interfaces.ifTable.ifEntry.ifPhysAddress.1=00_00_00_00_00_00 interfaces.ifTable.ifEntry.ifPhysAddress.2=00_00_00_00_00_00 interfaces.ifTable.ifEntry.ifPhysAddress.3=e4_a8_b6_e4_44_b0 interfaces.ifTable.ifEntry.ifPhysAddress.4=e4_a8_b6_e4_44_b0 interfaces.ifTable.ifEntry.ifPhysAddress.5=e4_a8_b6_e4_44_b0 interfaces.ifTable.ifEntry.ifPhysAddress.6=e4_a8_b6_e4_44_b0 } }
12:52:58.406302 IP (tos 0x0, ttl 63, id 13715, offset 0, flags [DF], proto UDP (17), length 83)
    mysnmphost.47247 > 10.0.232.216.snmp: [bad udp cksum 0x8ecc -> 0xa0da!]  { SNMPv2c C="SnmP_" { GetBulk(30) R=1217588380  N=0 M=50 31.1.1.1.18 } }
12:52:58.620271 IP (tos 0x0, ttl 249, id 62511, offset 0, flags [+], proto UDP (17), length 1500)
    10.0.232.216.snmp > mysnmphost.47247:  [len1468<asnlen1504]
12:52:58.620285 IP (tos 0x0, ttl 249, id 62511, offset 1480, flags [none], proto UDP (17), length 56)
    10.0.232.216 > mysnmphost: udp
@cemremengu
Copy link
Contributor Author

cemremengu commented Dec 17, 2021 •
edited
Loading

Removing this check to return nil instead, fixes the problem but I am not sure why yet. When I check OIDs inside the returned SnmpPDU everything looks fine. So maybe this is not an error after all ?

image

@kintansky
Copy link

Same here. I think return nil as error should be fine.

@Chunters
Copy link

Chunters commented Jan 28, 2022 •
edited
Loading

Same problem with oid .1.3.6.1.2.1.17.1.4.1.2
When use BulkWalkAll
"error in unmarshalResponse: error decoding value: error parsing OID Value: invalid OID length"

When use WalkAll - all fine.

snmpbulkwalk - correctly processes the request

snmpbulkwalk -v2c -c*** 10.221.172.253 .1.3.6.1.2.1.17.1.4.1.2
SNMPv2-SMI::mib-2.17.1.4.1.2.3 = INTEGER: 17410
SNMPv2-SMI::mib-2.17.1.4.1.2.4 = INTEGER: 17411
SNMPv2-SMI::mib-2.17.1.4.1.2.5 = INTEGER: 17412
SNMPv2-SMI::mib-2.17.1.4.1.2.6 = INTEGER: 17413
SNMPv2-SMI::mib-2.17.1.4.1.2.7 = INTEGER: 17414
SNMPv2-SMI::mib-2.17.1.4.1.2.8 = INTEGER: 17415
SNMPv2-SMI::mib-2.17.1.4.1.2.9 = INTEGER: 17416
SNMPv2-SMI::mib-2.17.1.4.1.2.10 = INTEGER: 17417
SNMPv2-SMI::mib-2.17.1.4.1.2.11 = INTEGER: 17418
SNMPv2-SMI::mib-2.17.1.4.1.2.12 = INTEGER: 17419
SNMPv2-SMI::mib-2.17.1.4.1.2.13 = INTEGER: 17420
SNMPv2-SMI::mib-2.17.1.4.1.2.14 = INTEGER: 17421
SNMPv2-SMI::mib-2.17.1.4.1.2.15 = INTEGER: 17422
SNMPv2-SMI::mib-2.17.1.4.1.2.16 = INTEGER: 17423
SNMPv2-SMI::mib-2.17.1.4.1.2.17 = INTEGER: 17424
SNMPv2-SMI::mib-2.17.1.4.1.2.18 = INTEGER: 17425
SNMPv2-SMI::mib-2.17.1.4.1.2.19 = INTEGER: 17426
SNMPv2-SMI::mib-2.17.1.4.1.2.20 = INTEGER: 17427
SNMPv2-SMI::mib-2.17.1.4.1.2.21 = INTEGER: 17428
SNMPv2-SMI::mib-2.17.1.4.1.2.22 = INTEGER: 17429
SNMPv2-SMI::mib-2.17.1.4.1.2.23 = INTEGER: 17430
SNMPv2-SMI::mib-2.17.1.4.1.2.24 = INTEGER: 17431
SNMPv2-SMI::mib-2.17.1.4.1.2.25 = INTEGER: 17432
SNMPv2-SMI::mib-2.17.1.4.1.2.26 = INTEGER: 17433
SNMPv2-SMI::mib-2.17.1.4.1.2.27 = INTEGER: 17474
SNMPv2-SMI::mib-2.17.1.4.1.2.28 = INTEGER: 17475
SNMPv2-SMI::mib-2.17.1.4.1.2.29 = INTEGER: 17538
SNMPv2-SMI::mib-2.17.1.4.1.2.30 = INTEGER: 17539

After doing some research, I came to the conclusion that the problem may be in the wrong type of data that the device produces.
Wireshark shows that an incorrect data type and/or value is being received.

image
image

How does it look in snmpbulkwalk on incorrect device

snmpbulkwalk -v2c -c*** -On 10.221.172.253 1.3.6.1.2.1.17.1.4.1.3
.1.3.6.1.2.1.17.1.4.1.3.3 = OID: .0
.1.3.6.1.2.1.17.1.4.1.3.4 = OID: .0
.1.3.6.1.2.1.17.1.4.1.3.5 = OID: .0
.1.3.6.1.2.1.17.1.4.1.3.6 = OID: .0
.1.3.6.1.2.1.17.1.4.1.3.7 = OID: .0
.1.3.6.1.2.1.17.1.4.1.3.8 = OID: .0
.1.3.6.1.2.1.17.1.4.1.3.9 = OID: .0
.1.3.6.1.2.1.17.1.4.1.3.10 = OID: .0
.1.3.6.1.2.1.17.1.4.1.3.11 = OID: .0
.1.3.6.1.2.1.17.1.4.1.3.12 = OID: .0
.1.3.6.1.2.1.17.1.4.1.3.13 = OID: .0
.1.3.6.1.2.1.17.1.4.1.3.14 = OID: .0
.1.3.6.1.2.1.17.1.4.1.3.15 = OID: .0
.1.3.6.1.2.1.17.1.4.1.3.16 = OID: .0
.1.3.6.1.2.1.17.1.4.1.3.17 = OID: .0
.1.3.6.1.2.1.17.1.4.1.3.18 = OID: .0
.1.3.6.1.2.1.17.1.4.1.3.19 = OID: .0
.1.3.6.1.2.1.17.1.4.1.3.20 = OID: .0
.1.3.6.1.2.1.17.1.4.1.3.21 = OID: .0
.1.3.6.1.2.1.17.1.4.1.3.22 = OID: .0
.1.3.6.1.2.1.17.1.4.1.3.23 = OID: .0
.1.3.6.1.2.1.17.1.4.1.3.24 = OID: .0
.1.3.6.1.2.1.17.1.4.1.3.25 = OID: .0
.1.3.6.1.2.1.17.1.4.1.3.26 = OID: .0
.1.3.6.1.2.1.17.1.4.1.3.27 = OID: .0
.1.3.6.1.2.1.17.1.4.1.3.28 = OID: .0
.1.3.6.1.2.1.17.1.4.1.3.29 = OID: .0
.1.3.6.1.2.1.17.1.4.1.3.30 = OID: .0

snmpbulkwalk -v2c -c*** 10.221.172.253 1.3.6.1.2.1.17.1.4.1.3
SNMPv2-SMI::mib-2.17.1.4.1.3.3 = OID: ccitt
SNMPv2-SMI::mib-2.17.1.4.1.3.4 = OID: ccitt
SNMPv2-SMI::mib-2.17.1.4.1.3.5 = OID: ccitt
SNMPv2-SMI::mib-2.17.1.4.1.3.6 = OID: ccitt
SNMPv2-SMI::mib-2.17.1.4.1.3.7 = OID: ccitt
SNMPv2-SMI::mib-2.17.1.4.1.3.8 = OID: ccitt
SNMPv2-SMI::mib-2.17.1.4.1.3.9 = OID: ccitt
SNMPv2-SMI::mib-2.17.1.4.1.3.10 = OID: ccitt
SNMPv2-SMI::mib-2.17.1.4.1.3.11 = OID: ccitt
SNMPv2-SMI::mib-2.17.1.4.1.3.12 = OID: ccitt
SNMPv2-SMI::mib-2.17.1.4.1.3.13 = OID: ccitt
SNMPv2-SMI::mib-2.17.1.4.1.3.14 = OID: ccitt
SNMPv2-SMI::mib-2.17.1.4.1.3.15 = OID: ccitt
SNMPv2-SMI::mib-2.17.1.4.1.3.16 = OID: ccitt
SNMPv2-SMI::mib-2.17.1.4.1.3.17 = OID: ccitt
SNMPv2-SMI::mib-2.17.1.4.1.3.18 = OID: ccitt
SNMPv2-SMI::mib-2.17.1.4.1.3.19 = OID: ccitt
SNMPv2-SMI::mib-2.17.1.4.1.3.20 = OID: ccitt
SNMPv2-SMI::mib-2.17.1.4.1.3.21 = OID: ccitt
SNMPv2-SMI::mib-2.17.1.4.1.3.22 = OID: ccitt
SNMPv2-SMI::mib-2.17.1.4.1.3.23 = OID: ccitt
SNMPv2-SMI::mib-2.17.1.4.1.3.24 = OID: ccitt
SNMPv2-SMI::mib-2.17.1.4.1.3.25 = OID: ccitt
SNMPv2-SMI::mib-2.17.1.4.1.3.26 = OID: ccitt
SNMPv2-SMI::mib-2.17.1.4.1.3.27 = OID: ccitt
SNMPv2-SMI::mib-2.17.1.4.1.3.28 = OID: ccitt
SNMPv2-SMI::mib-2.17.1.4.1.3.29 = OID: ccitt
SNMPv2-SMI::mib-2.17.1.4.1.3.30 = OID: ccitt

image
image

How does it look in snmpbulkwalk on correct device

snmpbulkwalk -v2c -c*** -On 10.221.187.121 1.3.6.1.2.1.17.1.4.1.3
.1.3.6.1.2.1.17.1.4.1.3.1 = OID: .0.0
.1.3.6.1.2.1.17.1.4.1.3.2 = OID: .0.0
.1.3.6.1.2.1.17.1.4.1.3.3 = OID: .0.0
.1.3.6.1.2.1.17.1.4.1.3.4 = OID: .0.0
.1.3.6.1.2.1.17.1.4.1.3.5 = OID: .0.0
.1.3.6.1.2.1.17.1.4.1.3.6 = OID: .0.0
.1.3.6.1.2.1.17.1.4.1.3.7 = OID: .0.0
.1.3.6.1.2.1.17.1.4.1.3.8 = OID: .0.0
.1.3.6.1.2.1.17.1.4.1.3.9 = OID: .0.0
.1.3.6.1.2.1.17.1.4.1.3.10 = OID: .0.0
.1.3.6.1.2.1.17.1.4.1.3.11 = OID: .0.0
.1.3.6.1.2.1.17.1.4.1.3.12 = OID: .0.0
.1.3.6.1.2.1.17.1.4.1.3.13 = OID: .0.0
.1.3.6.1.2.1.17.1.4.1.3.14 = OID: .0.0
.1.3.6.1.2.1.17.1.4.1.3.15 = OID: .0.0
.1.3.6.1.2.1.17.1.4.1.3.16 = OID: .0.0
.1.3.6.1.2.1.17.1.4.1.3.17 = OID: .0.0
.1.3.6.1.2.1.17.1.4.1.3.18 = OID: .0.0
.1.3.6.1.2.1.17.1.4.1.3.19 = OID: .0.0
.1.3.6.1.2.1.17.1.4.1.3.20 = OID: .0.0
.1.3.6.1.2.1.17.1.4.1.3.21 = OID: .0.0
.1.3.6.1.2.1.17.1.4.1.3.22 = OID: .0.0
.1.3.6.1.2.1.17.1.4.1.3.23 = OID: .0.0
.1.3.6.1.2.1.17.1.4.1.3.24 = OID: .0.0
.1.3.6.1.2.1.17.1.4.1.3.25 = OID: .0.0
.1.3.6.1.2.1.17.1.4.1.3.26 = OID: .0.0
snmpbulkwalk -v2c -c*** 10.221.187.121 1.3.6.1.2.1.17.1.4.1.3
SNMPv2-SMI::mib-2.17.1.4.1.3.1 = OID: SNMPv2-SMI::zeroDotZero
SNMPv2-SMI::mib-2.17.1.4.1.3.2 = OID: SNMPv2-SMI::zeroDotZero
SNMPv2-SMI::mib-2.17.1.4.1.3.3 = OID: SNMPv2-SMI::zeroDotZero
SNMPv2-SMI::mib-2.17.1.4.1.3.4 = OID: SNMPv2-SMI::zeroDotZero
SNMPv2-SMI::mib-2.17.1.4.1.3.5 = OID: SNMPv2-SMI::zeroDotZero
SNMPv2-SMI::mib-2.17.1.4.1.3.6 = OID: SNMPv2-SMI::zeroDotZero
SNMPv2-SMI::mib-2.17.1.4.1.3.7 = OID: SNMPv2-SMI::zeroDotZero
SNMPv2-SMI::mib-2.17.1.4.1.3.8 = OID: SNMPv2-SMI::zeroDotZero
SNMPv2-SMI::mib-2.17.1.4.1.3.9 = OID: SNMPv2-SMI::zeroDotZero
SNMPv2-SMI::mib-2.17.1.4.1.3.10 = OID: SNMPv2-SMI::zeroDotZero
SNMPv2-SMI::mib-2.17.1.4.1.3.11 = OID: SNMPv2-SMI::zeroDotZero
SNMPv2-SMI::mib-2.17.1.4.1.3.12 = OID: SNMPv2-SMI::zeroDotZero
SNMPv2-SMI::mib-2.17.1.4.1.3.13 = OID: SNMPv2-SMI::zeroDotZero
SNMPv2-SMI::mib-2.17.1.4.1.3.14 = OID: SNMPv2-SMI::zeroDotZero
SNMPv2-SMI::mib-2.17.1.4.1.3.15 = OID: SNMPv2-SMI::zeroDotZero
SNMPv2-SMI::mib-2.17.1.4.1.3.16 = OID: SNMPv2-SMI::zeroDotZero
SNMPv2-SMI::mib-2.17.1.4.1.3.17 = OID: SNMPv2-SMI::zeroDotZero
SNMPv2-SMI::mib-2.17.1.4.1.3.18 = OID: SNMPv2-SMI::zeroDotZero
SNMPv2-SMI::mib-2.17.1.4.1.3.19 = OID: SNMPv2-SMI::zeroDotZero
SNMPv2-SMI::mib-2.17.1.4.1.3.20 = OID: SNMPv2-SMI::zeroDotZero
SNMPv2-SMI::mib-2.17.1.4.1.3.21 = OID: SNMPv2-SMI::zeroDotZero
SNMPv2-SMI::mib-2.17.1.4.1.3.22 = OID: SNMPv2-SMI::zeroDotZero
SNMPv2-SMI::mib-2.17.1.4.1.3.23 = OID: SNMPv2-SMI::zeroDotZero
SNMPv2-SMI::mib-2.17.1.4.1.3.24 = OID: SNMPv2-SMI::zeroDotZero
SNMPv2-SMI::mib-2.17.1.4.1.3.25 = OID: SNMPv2-SMI::zeroDotZero
SNMPv2-SMI::mib-2.17.1.4.1.3.26 = OID: SNMPv2-SMI::zeroDotZero

Can this problem be solved on the snmpgo side?

@Chunters
Copy link

Removing this check to return nil instead, fixes the problem but I am not sure why yet. When I check OIDs inside the returned SnmpPDU everything looks fine. So maybe this is not an error after all ?

image

@cemremengu This change helps, but I'm not sure if it's the correct solution. Because we won't get errors when they actually happen.

@cemremengu
Copy link
Contributor Author

@Chunters yes, this is just a workaround unfortunately since I am not sure how to correct this error otherwise, yet. Currently,I reverted to WalkAll.

net-snmp somehow handles this as you said so maybe that can be checked.

@TimRots
Copy link
Member

TimRots commented Mar 5, 2022

Not sure if we should gracefully handle situations like net-snmp appears to do.
@cemremengu If you share a pcap with the correct/incorrect responses I can try to take a look to see what we can do.

@barzog
Copy link

barzog commented Mar 7, 2023

Also hit this. Also mentioned here: influxdata/telegraf#10240
Would be sufficient to provide dump only with incorrect responses?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@cemremengu @TimRots @barzog @Chunters @kintansky