`SetDeadline not implemented` errors in proxy-go output
At da8b98d09089e32d53573a1cabcb450aa290b4c8, running proxy-go and getting assigned a client (as in comment:13:ticket:29258) causes a lot of output of this nature:
2019/10/17 19:47:02 connected to relay
2019/10/17 19:47:02 calling SetDeadline in Read returned the following error: SetDeadline not implemented
2019/10/17 19:47:02 calling SetDeadline in Read returned the following error: SetDeadline not implemented
2019/10/17 19:47:02 calling SetDeadline in Write returned the following error: SetDeadline not implemented
2019/10/17 19:47:02 Write 751 bytes --> WebRTC
2019/10/17 19:47:02 OnMessage <--- 126 bytes
2019/10/17 19:47:02 calling SetDeadline in Read returned the following error: SetDeadline not implemented
2019/10/17 19:47:02 calling SetDeadline in Write returned the following error: SetDeadline not implemented
2019/10/17 19:47:02 Write 51 bytes --> WebRTC
2019/10/17 19:47:02 OnMessage <--- 40 bytes
2019/10/17 19:47:02 calling SetDeadline in Read returned the following error: SetDeadline not implemented
2019/10/17 19:47:03 calling SetDeadline in Write returned the following error: SetDeadline not implemented
2019/10/17 19:47:03 Write 1508 bytes --> WebRTC
2019/10/17 19:47:03 OnMessage <--- 1057 bytes
2019/10/17 19:47:03 calling SetDeadline in Read returned the following error: SetDeadline not implemented
2019/10/17 19:47:03 calling SetDeadline in Write returned the following error: SetDeadline not implemented
2019/10/17 19:47:03 Write 543 bytes --> WebRTC
2019/10/17 19:47:03 OnMessage <--- 1057 bytes
2019/10/17 19:47:03 calling SetDeadline in Read returned the following error: SetDeadline not implemented
2019/10/17 19:47:03 calling SetDeadline in Write returned the following error: SetDeadline not implemented
I suppose the immediate cause is the changes from #31794 (moved).