an outstanding issue where the listen thread would take a while to disconnect after the socket was gone
fires ErrorResponses for Deepgram, Fatal, etc type error messages
Types of changes
What types of changes does your code introduce to the community Go SDK?
Put an x in the boxes that apply
[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update or tests (if none of the other choices apply)
Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.
Proposed changes
This fixes an issue with the last PR https://github.com/deepgram/deepgram-go-sdk/pull/232 which even OpenResponse didn't have a corresponding CloseResponse.
This also fixes:
Types of changes
What types of changes does your code introduce to the community Go SDK? Put an
xin the boxes that applyChecklist
Put an
xin the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.Further comments
NA