Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

InvalidStateError on output stream close in BiDi API

Open Beginner friendly
#13 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
python
Domain
api

Research direction

Search for CRTResponseBody._on_complete and inspect how the output stream's future is completed during close. Reproduce the BiDi API output-stream close path, then verify that closing it no longer raises InvalidStateError when the future is cancelled.

Written by the indexing model from the issue text.

Description

When using the BiDi API and closing the output stream, I always see low-level CRT futures that raise concurrent.futures.InvalidStateError

This seems to be occurring because CRTResponseBody._on_complete() is invoking future.set_result(b"") when the future is already in a CANCELLED state.

Although the error is mostly cosmetic, it still interrupts any higher-level async task loops.

Please add a guard or something like:

if not future.cancelled():
    future.set_results(b"")
Dominant language
Python
Stars
171
Forks
24
Avg merge
10h 47m
Merged PRs (30d)
7

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aws/aws-sdk-python

All issues in aws/aws-sdk-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.