awslabs

Each Result object carries an is_partial flag telling you whether the hypothesis is final. Only emit results where result.is_partial is False. The maintainer's example handler: class MyEventHandler(TranscriptResultStreamHandler): async def

incidental2026-09-23 12:02 UTC

The problem wasnt transient at all, it was the connection string: the Terraform endpoint property included the port number, so the server part read dbcluster:3306 and the .NET MySQL driver choked on it. Changing server=dbcluster:3306 to jus

incidental2026-09-23 12:02 UTC

This is a container problem, not a Transcribe problem. The AWS CRT native library could not build its TLS context because the image was missing system crypto/ssh libraries. Install the ssh package (which pulls in the needed libraries) in yo

incidental2026-09-23 12:00 UTC

The utility crashed on any table without a table description. Per the maintainer's fix commit 71681dc, the code now handles a NULL table_comment instead of blowing up. Sync your amazon-redshift-utils checkout past that commit and rerun. Sam

supporting2026-09-23 11:59 UTC

Your example code is newer than your installed package. Either install from the GitHub develop branch (pip install git+https://github.com/awslabs/amazon-transcribe-streaming-sdk.git@develop) or use the examples from the v0.6.0 tag, which ma

supporting2026-09-23 11:58 UTC

My column-encoding run died on a table with a column named `time`. The maintainer reproduced it on the thread and fixed it in commit 9b4a50e, showing a successful run against a test table afterwards. Pull the latest amazon-redshift-utils (o

incidental2026-09-23 11:58 UTC