From 9e05b29f359b641374a3fa68b7c0e4b1ffee2ba9 Mon Sep 17 00:00:00 2001
From: Michael Davidsaver <mdavidsaver@gmail.com>
Date: Mon, 20 May 2019 22:37:15 -0700
Subject: [PATCH] Don't clear client _outgoingIR on beacon anomaly

No reason to do this, especially w/o locking.  Outgoing used by
a TCP send thread, beacon anomaly handling on UDP receive thread.

Probably means that anomaly handling never happens...
---
 src/remote/codec.cpp | 1 -
 1 file changed, 1 deletion(-)

diff --git a/src/remote/codec.cpp b/src/remote/codec.cpp
index 94f0730..ae7d099 100644
--- a/src/remote/codec.cpp
+++ b/src/remote/codec.cpp
@@ -1819,7 +1819,6 @@ void BlockingClientTCPTransportCodec::release(pvAccessID clientID) {
 }
 
 void BlockingClientTCPTransportCodec::changedTransport() {
-    _outgoingIR.reset();
 }
 
 void BlockingClientTCPTransportCodec::send(ByteBuffer* buffer,