Fix seq_no persisting across sessions (#33)

* Fix seq_no persisting across sessions When using an instance of the client to run multiple sessions (calling .run multiple times), the seq_no of the subsequent sessions didn't start with a zero. Now it does, so we send the same messages regardless of using single or multiple client instances to run multiple sessions. * Update CHANGELOG.md * Update VERSION Co-authored-by: Viren Nadkarni <virenn@speechmatics.com>
speechmatics · Feb 11, 2021 · 1b55433 · 1b55433
1 parent d223de1
commit 1b55433
Show file tree

Hide file tree

Showing 3 changed files with 9 additions and 1 deletion.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -8,6 +8,13 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [Unreleased]
 
 
+## [0.0.12] - 2021-02-10
+
+### Fixed
+
+- Fix seq_no persisting across sessions
+
+
 ## [0.0.11] - 2020-10-18
 
 ### Changed

diff --git a/VERSION b/VERSION
@@ -1 +1 @@
-0.0.11
+0.0.12
diff --git a/speechmatics/client.py b/speechmatics/client.py
@@ -319,6 +319,7 @@ async def run(self, stream, transcription_config, audio_settings):
             consumer/producer tasks.
         """
         self.transcription_config = transcription_config
+        self.seq_no = 0
         await self._init_synchronization_primitives()
 
         extra_headers = dict()