Srinivas Sakhamuri
Srinivas Sakhamuri
This seems to work fine for us with web-sockets, i.e. web-socket reconnects within configured thresholds. But we did observe full reload when there is a shard change. We would like...
Shouldn't it gracefully return error when the stats are not available for e.g. ethtool just returns stats not available ``` $ sudo /sbin/ethtool -S ens3 no stats available ```
Here is the stack with latest commit ``` Interface name: ens3f0np0 panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xea5c11] goroutine 76...