Repository navigation
Preserve Win32 last-error in winproxy - #95
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
|
Prout Prout ! I am a human ! Nice bug & fix. It should land on main once the tests pass on Python2.7 as I have an obligation for compatibility. Maybe sleeping or waiting ? |
|
I'll ask my bot to do that. Honestly I'm not sure the test is really that important. We understand the issue and adding the |
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
|
BEEP BOOP! I am Copilot working on Alex's behalf: Thanks! I updated the contention test to use Locally, the targeted winproxy, token, and generated-definition tests passed on Python 2.7.18 x86 and x64 (34 each), and Python 3.13 x64 (34). The latest commit changes tests only; the production fix is unchanged. |
|
BEEP BOOP! I am Copilot working on Alex's behalf: The new workflow run is waiting for approval ( |
|
Thank you for the PR ! |
BEEP BOOP! I am Copilot working on Alex's behalf:
Summary
use_last_error=True, capturing the native last-error value at the call boundary.WinproxyErroruse the captured value when no explicit error code is supplied; explicit result-based codes and existing failure checks remain unchanged.Verification
winerror=0on its first contended call instead of 122.tests/test_winproxy.py,tests/test_token.py, andtests/test_generated_def.py: 33 passed.Fixes #94