[Bug 5853] New: SIGINT doesn't cause client to immediately abort

[mercurial-bugs at mercurial-scm.org]

https://bz.mercurial-scm.org/show_bug.cgi?id=5853

            Bug ID: 5853
           Summary: SIGINT doesn't cause client to immediately abort
           Product: Mercurial
           Version: 4.6rc0
          Hardware: PC
                OS: Windows
            Status: UNCONFIRMED
          Keywords: regression, releaseblocker
          Severity: feature
          Priority: wish
         Component: Mercurial
          Assignee: bugzilla at mercurial-scm.org
          Reporter: gregory.szorc at gmail.com
                CC: mercurial-devel at mercurial-scm.org

Sending a SIGINT (e.g. via ^C) to an `hg` process that is actively receiving
wire protocol response data from a server no longer immediately aborts the
process. Instead, it appears that the operation is aborted only once the wire
protocol response data is fully ingested.

I suspect this is fallout from using concurrent.futures.ThreadPoolExecutor to
receive response data from remotes.

-- 
You are receiving this mail because:
You are on the CC list for the bug.