rpctransport/tty: Fix TypeError when TTY client is closed

The executor that reads the serial port is not terminated gracefully by
aioserial when close is called and thus it touches some variables set to
`Note` at that point causing `TypeError` to be raised. We handle this as
disconnect because it should happen only on disconnect.

The fix seems to be present in PR
mrjohannchang/aioserial.py#7 but it seems that
development of this project somewhat stalled. We should think about
moving to some alternative if nothing happens in year or two.

CHANGELOG.md

@@ -4,6 +4,11 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [Unreleased]
+### Fixed
+- Close of TTY client causing `TypeError` to be raised in receive task
+
+
 ## [0.7.3] - 2024-10-31
 ### Fixed
 - Invalid unpack of date and time from ChainPack for dates before 2018-02-02

shv/rpctransport/tty.py

@@ -75,7 +75,10 @@ async def _read_exactly(self, n: int) -> bytes:
         while len(res) < n:
             try:
                 res += await self.serial.read_async(n - len(res))
-            except aioserial.SerialException as exc:
+            # Note: TypeError is raised because serial.close() clears some
+            # variables that are still used in the task. This is bug in
+            # aioserial.
+            except (aioserial.SerialException, TypeError) as exc:
                 self._eof.set()
                 raise EOFError from exc
         return res