Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Attempted fix for "unexpected cancel" issue in #34 #35

Merged
merged 5 commits into from
Feb 28, 2022
Merged

Attempted fix for "unexpected cancel" issue in #34 #35

merged 5 commits into from
Feb 28, 2022

Commits on Feb 19, 2022

  1. Test for "unexpected cancel" scenario

    @bdowning
    bdowning committed Feb 19, 2022
    Configuration menu
    Copy the full SHA
    08499c1 View commit details
    Browse the repository at this point in the history

  2. Attempted fix for "unexpected cancel" scenario

    @bdowning
    bdowning committed Feb 19, 2022
    Configuration menu
    Copy the full SHA
    0f0e32d View commit details
    Browse the repository at this point in the history

  3. Changelog message

    @bdowning
    bdowning committed Feb 19, 2022
    Configuration menu
    Copy the full SHA
    07ed0fb View commit details
    Browse the repository at this point in the history

Commits on Feb 27, 2022

  1. Fix the right place 

    * Take the implementation of `_is_base_error()` from Python 3.11's
  `asyncio.TaskGroup` instead of changing `__aexit__()` method.
* Use more specific exception class in the test case to prevent
  unintended catch-all situation in terms of regression check.
    @achimnol
    achimnol committed Feb 27, 2022
    Configuration menu
    Copy the full SHA
    7f4b8e4 View commit details
    Browse the repository at this point in the history

  2. Add more description to test case

    @achimnol
    achimnol committed Feb 27, 2022
    Configuration menu
    Copy the full SHA
    1db75c9 View commit details
    Browse the repository at this point in the history