Re: Trouble with defaults and timeout decorator

On 24/06/2023 18.18, Jason Friedman wrote: I'm writing a database connectivity module to be used by other modules and leveraging the jaydebeapi module. From what I can tell jaydebeapi contains no built-in timeout capability, so then I turned to https://pypi.org/project/timeout-decorator/. My

Re: Trouble with defaults and timeout decorator

On 2023-06-24 17:18, Jason Friedman via Python-list wrote: I'm writing a database connectivity module to be used by other modules and leveraging the jaydebeapi module. From what I can tell jaydebeapi contains no built-in timeout capability, so then I turned to https://pypi.org/project/timeout

Trouble with defaults and timeout decorator

I'm writing a database connectivity module to be used by other modules and leveraging the jaydebeapi module. >From what I can tell jaydebeapi contains no built-in timeout capability, so then I turned to https://pypi.org/project/timeout-decorator/. My goal is to have a default timeout of, say,

[issue439823] poll docs should mention timeout unit

Change by admin : -- github: None -> 34714 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue461321] Fix timeout=None in asyncore.py

Change by admin : -- github: None -> 35164 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue47106] test_asyncio: test_shutdown_cleanly() failed with timeout (10 seconds) on slow x86 Gentoo Non-Debug with X 3.x

New submission from STINNER Victor : test_shutdown_cleanly() of test_asyncio failed on x86 Gentoo Non-Debug with X 3.x with a timeout of 10 seconds: https://buildbot.python.org/all/#/builders/58/builds/1958 asyncio uses a default timeout of 60 seconds for a TLS handshake, but the test takes

[issue46716] regrtest didn't respect the timeout when running test_subprocess on AMD64 Windows11 3.x

Change by Jeremy Kloth : -- pull_requests: +30168 pull_request: https://github.com/python/cpython/pull/32081 ___ Python tracker ___

[issue46716] regrtest didn't respect the timeout when running test_subprocess on AMD64 Windows11 3.x

Change by Jeremy Kloth : -- keywords: +patch pull_requests: +30167 stage: -> patch review pull_request: https://github.com/python/cpython/pull/32079 ___ Python tracker ___

[issue46999] test_multiprocessing_fork running without any timeout

is usually limited to 4-6 cores and 20GB of RAM (including swap). What else could be an issue for these hangs? How can this test reliably timeout? I know it takes a few hours on slow architectures even when succeeding. -- components: Tests messages: 415027 nosy: doko priority: normal

[issue46716] regrtest didn't respect the timeout when running test_subprocess on AMD64 Windows11 3.x

STINNER Victor added the comment: > It does seem that only the Windows Popen._wait() cannot handle negative > timeout values, so the fix should be as simple as coercing the timeout values > to >= 0. Oh. This function should maybe raise an exception if the timeout is negativ

[issue46679] test.support.wait_process ignores timeout argument

Change by Nikita Sobolev : -- nosy: +sobolevn nosy_count: 1.0 -> 2.0 pull_requests: +29486 pull_request: https://github.com/python/cpython/pull/31274 ___ Python tracker ___

[issue46716] regrtest didn't respect the timeout when running test_subprocess on AMD64 Windows11 3.x

Eryk Sun added the comment: > 4) use Job objects to group Windows processes for termination I think a separate issue should be created for this enhancement. _winapi wrappers would be needed for CreateJobObjectW(), SetInformationJobObject(), AssignProcessToJobObject(), TerminatejobObject(),

[issue46716] regrtest didn't respect the timeout when running test_subprocess on AMD64 Windows11 3.x

andard library. No third-party package or application should use _winapi directly. > 1) modify Windows Popen._wait() to raise on out of bounds > values [< 0 or >= INFINITE] I think raising ValueError would be best at this level. For example:

[issue46716] regrtest didn't respect the timeout when running test_subprocess on AMD64 Windows11 3.x

Jeremy Kloth added the comment: > > the fix should be as simple as coercing the timeout values to >= 0. > > Popen._remaining_time() should return max(endtime - _time(), 0). That was my first initial instinct as well, however, that change would also affect more of the Popen be

[issue46716] regrtest didn't respect the timeout when running test_subprocess on AMD64 Windows11 3.x

Eryk Sun added the comment: > the fix should be as simple as coercing the timeout values to >= 0. Popen._remaining_time() should return max(endtime - _time(), 0). Popen._wait() should raise OverflowError if the timeout is too large for the implementation. In Windows, the upper

[issue46716] regrtest didn't respect the timeout when running test_subprocess on AMD64 Windows11 3.x

Jeremy Kloth added the comment: I've been able locally to reproduce the test_subprocess hang. The responsible function is subprocess.run(). The test case, test_timeout(), uses a small timeout value (0.0001), which, when given enough load, can cause the run() call to hang. A judicious use

[issue46716] regrtest didn't respect the timeout when running test_subprocess on AMD64 Windows11 3.x

to the job. Post WM_CLOSE to each window in the job. A process might ignore a request to close. It could keep the window open or continue running in the background. After an internal timeout, you can call TerminateJobObject() to kill any process in the job that remains alive. This is a forced and ab

[issue46711] test_logging: test_post_fork_child_no_deadlock() failed with timeout on AMD64 Arch Linux Asan Debug 3.10

Change by Nikita Sobolev : -- keywords: +patch nosy: +sobolevn nosy_count: 1.0 -> 2.0 pull_requests: +29436 stage: -> patch review pull_request: https://github.com/python/cpython/pull/31274 ___ Python tracker

[issue46716] regrtest didn't respect the timeout when running test_subprocess on AMD64 Windows11 3.x

Jeremy Kloth added the comment: The test only completed once I purposefully terminated the offending Python process. The only identifying information I noticed was the command-line of `-c "while True: pass"`, indicating it was stuck in either test_call_timeout() or test_timeout() in

[issue46716] regrtest didn't respect the timeout when running test_subprocess on AMD64 Windows11 3.x

Change by STINNER Victor : -- title: regrtest didn't respect the timeout on AMD64 Windows11 3.x -> regrtest didn't respect the timeout when running test_subprocess on AMD64 Windows11 3.x ___ Python tracker <https://bugs.python.org/issu

[issue46716] regrtest didn't respect the timeout on AMD64 Windows11 3.x

New submission from STINNER Victor : regrtest was run with --timeout 900 on AMD64 Windows11 3.x: timeout confirmed by "(timeout: 15 min, worker timeout: 20 min)" log. But then test_subprocss was only stopped after "4 hour 55 min". If the regrtest main process is able to

[issue46711] test_logging: test_post_fork_child_no_deadlock() failed with timeout on AMD64 Arch Linux Asan Debug 3.10

New submission from STINNER Victor : The test calls support.wait_process() which uses SHORT_TIMEOUT. wait_process() should use LONG_TIMEOUT, or the ASAN buildbot should increase its timeout (regrtest --timeout parameter). IMO using LONG_TIMEOUT is fine: it's ok if the test takes 2 minutes

[issue46679] test.support.wait_process ignores timeout argument

Change by Jason Wilkes : -- keywords: +patch pull_requests: +29375 stage: -> patch review pull_request: https://github.com/python/cpython/pull/31205 ___ Python tracker ___

[issue46679] test.support.wait_process ignores timeout argument

New submission from Jason Wilkes : The function wait_process in Lib/test/support/__init__.py ignores its timeout argument. This argument is useful, for example, in tests that need to determine whether a deadlock has been fixed (e.g., in PR-30310). Will submit a pull request to fix

[issue46625] timeout option of socket.create_connection is not respected

New submission from Nicolas SURRIBAS : When passing to socket.create_connection a timeout option above (approximately) 127 seconds, the timeout is not respected. Code to reproduce the issue : import socket from time import monotonic print(socket.getdefaulttimeout()) start = monotonic() try

[issue41711] Socker send method throws a timeout exception

Change by Irit Katriel : -- stage: -> resolved status: pending -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue28982] multiprocessing.Queue.get(block=True, timeout=0) always raises queue.Empty

Change by Irit Katriel : -- stage: -> resolved status: pending -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue46518] SSL socket timeout not set after client connects via accept

New submission from tomazas : Once a client connects to a SSL server over socket accept() the newly returned client socket `newsock` is wrapped in SSL context. Since the new client `newsock` does not have a socket timeout set (i.e. None), the final returned SSL context socket is also assigned

[issue31991] Race condition in wait with timeout for multiprocessing.Event

Irit Katriel added the comment: Python 3.6 is no longer maintained and I failed to reproduce this on a Mac on 3.11. Please create a new issue if you are seeing the problem on a current python version (>= 3.9) and specify which system you are running it on. -- nosy: +iritkatriel

[issue41857] Document timeout arguments to poll() in select module

Tal Einat added the comment: Thanks for this improvement, Zane! -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue41857] Document timeout arguments to poll() in select module

Tal Einat added the comment: New changeset 656971e4953a70a6048170377888db5530eea0a6 by Tal Einat in branch '3.9': [3.9] bpo-41857: mention timeout argument units in select.poll() and select.depoll() doc-strings (GH-22406) https://github.com/python/cpython/commit

[issue41857] Document timeout arguments to poll() in select module

Tal Einat added the comment: New changeset f6e5972fa984c10d47694973db1c91c6486d654a by Tal Einat in branch '3.10': [3.10] bpo-41857: mention timeout argument units in select.poll() and select.depoll() doc-strings (GH-22406) https://github.com/python/cpython/commit

[issue41857] Document timeout arguments to poll() in select module

Change by Tal Einat : -- pull_requests: +28929 pull_request: https://github.com/python/cpython/pull/30742 ___ Python tracker ___

[issue41857] Document timeout arguments to poll() in select module

Change by Tal Einat : -- pull_requests: +28928 pull_request: https://github.com/python/cpython/pull/30741 ___ Python tracker ___

[issue28982] multiprocessing.Queue.get(block=True, timeout=0) always raises queue.Empty

Irit Katriel added the comment: On 3.11 I get this on both Mac and windows: >>> from multiprocessing import Queue >>> q = Queue() >>> q.put('foo') >>> q.get(True, 0) # raises Empty 'foo' -- nosy: +iritkatriel resolution: -> out of date status: open -> pending

[issue41857] Document timeout arguments to poll() in select module

Tal Einat added the comment: New changeset 27df7566bc19699b967e0e30d7808637b90141f6 by Zane Bitter in branch 'main': bpo-41857: mention timeout argument units in select.poll() and select.depoll() doc-strings (GH-22406) https://github.com/python/cpython/commit

[issue41857] Document timeout arguments to poll() in select module

Change by Tal Einat : -- versions: +Python 3.11, Python 3.9 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue41711] Socker send method throws a timeout exception

Irit Katriel added the comment: The timeout is mentioned in the documentation of create_connection, and of its getter and setter. It applies to many operations on the socket, but not mentioned for each method. Since it's pretty standard to have a timeout for network operations, I think

[issue46203] Add timeout for Windows build steps

Change by Mark Dickinson : -- stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bugs-list

[issue46203] Add timeout for Windows build steps

Change by Mark Dickinson : -- keywords: +patch pull_requests: +28513 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30301 ___ Python tracker ___

[issue46203] Add timeout for Windows build steps

New submission from Mark Dickinson : Recently there was an upstream issue with GitHub Actions that caused the Windows build steps in build.yml to hang. No output for the step was displayed in the build logs until the entire job was eventually cancelled, after the default step timeout of 6

[issue4079] urllib.request.Request 'timeout' attribute needs to have a default

Change by Alex Waygood : -- title: urllib.requst.Request 'timeout' attribute needs to have a default -> urllib.request.Request 'timeout' attribute needs to have a default ___ Python tracker <https://bugs.python.org/iss

[issue4079] urllib.requst.Request 'timeout' attribute needs to have a default

Terry J. Reedy added the comment: urllib2 became urllib.request in 3.x. In 2.6, 'timeout' became a parameter of both urlopen and OpenerDirector.open. In both cases the default was and is the 'global default timeout setting'. So 'timeout' has a default. Both functions take a Request

Re: Set git config credential.helper cache and timeout via python

> > > Hey All, > > I have a set of bash and python scripts that all interact with a remote > git repository. > > > https://gitpython.readthedocs.io/en/stable/reference.html?highlight=cache#git.index.fun.read_cache > https://pypi.org/project/git-credential-helpers/ > > But neither means appears to

Re: Set git config credential.helper cache and timeout via python

> Hey All, > > I have a set of bash and python scripts that all interact with a remote > git repository. > This does not exactly answer your question, but whenever I have wanted to interact with (popular) software via Python I have checked to see if someone has already written that code for me.

Set git config credential.helper cache and timeout via python

the following commands in git to effectively enable the caching of credentials in memory for a predefined amount of time off the linux shell: git config credential.helper 'cache git config credential.helper 'cache --timeout=300' However, what is the best way to do so via Python?  I've read

[issue41710] threading.Lock.acquire(timeout) should use sem_clockwait(CLOCK_MONOTONIC)

STINNER Victor added the comment: bpo-33632 "undefined behaviour: signed integer overflow in threadmodule.c" has been fixed by this change: New changeset 833fdf126c8fe77fd17e8a8ffbc5c571b3bf64bd by Victor Stinner in branch 'main': bpo-41710: Add private _PyDeadline_Get() function (GH-28674)

[issue12706] timeout sentinel in ftplib and poplib documentation

Change by Irit Katriel : -- versions: +Python 3.10, Python 3.11, Python 3.9 -Python 3.5, Python 3.6, Python 3.7 ___ Python tracker ___

[issue33838] Very slow upload with http.client on Windows when setting timeout

Change by Ivan Konovalov : -- versions: +Python 3.10, Python 3.9 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue41710] threading.Lock.acquire(timeout) should use sem_clockwait(CLOCK_MONOTONIC)

STINNER Victor added the comment: New changeset 03bbc6066ff40c62edd57612be9150dcf1b123c8 by Victor Stinner in branch 'main': bpo-41710: Fix What's New Entry credit (GH-28962) https://github.com/python/cpython/commit/03bbc6066ff40c62edd57612be9150dcf1b123c8 --

[issue41710] threading.Lock.acquire(timeout) should use sem_clockwait(CLOCK_MONOTONIC)

Change by STINNER Victor : -- pull_requests: +27251 pull_request: https://github.com/python/cpython/pull/28962 ___ Python tracker ___

[issue41710] threading.Lock.acquire(timeout) should use sem_clockwait(CLOCK_MONOTONIC)

STINNER Victor added the comment: Jonas Norling: Thanks for the bug report! It's now fixed in 3.9, 3.10 and main branches. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.10, Python 3.9 ___

[issue41710] threading.Lock.acquire(timeout) should use sem_clockwait(CLOCK_MONOTONIC)

STINNER Victor added the comment: New changeset 0e1aeab5d7de3f328876aea8ccabbc6db146a883 by Miss Islington (bot) in branch '3.9': bpo-41710: PyThread_acquire_lock_timed() uses sem_clockwait() (GH-28671) (GH-28683)

[issue41710] threading.Lock.acquire(timeout) should use sem_clockwait(CLOCK_MONOTONIC)

STINNER Victor added the comment: New changeset 6df8c327532627d6a1993c52e8e4a9b34968 by Victor Stinner in branch '3.10': bpo-41710: PyThread_acquire_lock_timed() uses sem_clockwait() (GH-28671) https://github.com/python/cpython/commit/6df8c327532627d6a1993c52e8e4a9b34968 --

[issue41710] threading.Lock.acquire(timeout) should use sem_clockwait(CLOCK_MONOTONIC)

Change by miss-islington : -- nosy: +miss-islington nosy_count: 4.0 -> 5.0 pull_requests: +27047 pull_request: https://github.com/python/cpython/pull/28683 ___ Python tracker

[issue41710] threading.Lock.acquire(timeout) should use sem_clockwait(CLOCK_MONOTONIC)

STINNER Victor added the comment: New changeset 833fdf126c8fe77fd17e8a8ffbc5c571b3bf64bd by Victor Stinner in branch 'main': bpo-41710: Add private _PyDeadline_Get() function (GH-28674) https://github.com/python/cpython/commit/833fdf126c8fe77fd17e8a8ffbc5c571b3bf64bd --

[issue41710] threading.Lock.acquire(timeout) should use sem_clockwait(CLOCK_MONOTONIC)

STINNER Victor added the comment: New changeset 54957f16a63ecb6b15f77b01fa7c55ada892604a by Victor Stinner in branch 'main': bpo-41710: gc_collect_main() uses _PyTime_GetPerfCounter() (GH-28676) https://github.com/python/cpython/commit/54957f16a63ecb6b15f77b01fa7c55ada892604a --

[issue41710] threading.Lock.acquire(timeout) should use sem_clockwait(CLOCK_MONOTONIC)

STINNER Victor added the comment: New changeset 98d282700221234157159df4af76423d89490ad9 by Victor Stinner in branch 'main': bpo-41710: Fix PY_TIMEOUT_MAX on Windows (GH-28673) https://github.com/python/cpython/commit/98d282700221234157159df4af76423d89490ad9 --

[issue41710] threading.Lock.acquire(timeout) should use sem_clockwait(CLOCK_MONOTONIC)

Change by STINNER Victor : -- pull_requests: +27042 pull_request: https://github.com/python/cpython/pull/28676 ___ Python tracker ___

[issue41710] threading.Lock.acquire(timeout) should use sem_clockwait(CLOCK_MONOTONIC)

Change by STINNER Victor : -- pull_requests: +27039 pull_request: https://github.com/python/cpython/pull/28674 ___ Python tracker ___

[issue41710] threading.Lock.acquire(timeout) should use sem_clockwait(CLOCK_MONOTONIC)

Change by STINNER Victor : -- pull_requests: +27038 pull_request: https://github.com/python/cpython/pull/28673 ___ Python tracker ___

[issue41710] threading.Lock.acquire(timeout) should use sem_clockwait(CLOCK_MONOTONIC)

STINNER Victor added the comment: > There are already a number of closed bugs for this and related issues: bpo > 23428, bpo 31267, bpo 35747. Fixed bpo-12822 modified threading.Condition.wait(timeout) to use a monotonic clock: use pthread_condattr_setclock(CLOCK_MONOTONIC). bpo-2342

[issue12822] threading.Condition.wait(timeout) should use a monotonic clock: use pthread_condattr_setclock(CLOCK_MONOTONIC)

Change by STINNER Victor : -- title: NewGIL should use CLOCK_MONOTONIC if possible. -> threading.Condition.wait(timeout) should use a monotonic clock: use pthread_condattr_setclock(CLOCK_MONOTONIC) ___ Python tracker <https://bugs.pyth

[issue41710] threading.Lock.acquire(timeout) should use sem_clockwait(CLOCK_MONOTONIC)

Change by STINNER Victor : -- pull_requests: +27037 pull_request: https://github.com/python/cpython/pull/28672 ___ Python tracker ___

[issue41710] threading.Lock.acquire(timeout) should use sem_clockwait(CLOCK_MONOTONIC)

Change by STINNER Victor : -- pull_requests: +27036 pull_request: https://github.com/python/cpython/pull/28671 ___ Python tracker ___

[issue41710] threading.Lock.acquire(timeout) should use sem_clockwait(CLOCK_MONOTONIC)

(...) -- title: acquire(timeout) of threading.Lock and threading.Condition is affected by jumps in system time: Python should use sem_clockwait(CLOCK_MONOTONIC) -> threading.Lock.acquire(timeout) should use sem_clockwait(CLOCK_MONOTONIC) versions: +Python 3.11 -Python

[issue41710] acquire(timeout) of threading.Lock and threading.Condition is affected by jumps in system time: Python should use sem_clockwait(CLOCK_MONOTONIC)

STINNER Victor added the comment: New changeset 1ee0f94d16f150356a4b9b0a39d44ba1d2d5b9fc by Victor Stinner in branch 'main': bpo-41710: PyThread_acquire_lock_timed() uses sem_clockwait() (GH-28662) https://github.com/python/cpython/commit/1ee0f94d16f150356a4b9b0a39d44ba1d2d5b9fc --

[issue41710] acquire(timeout) of threading.Lock and threading.Condition is affected by jumps in system time: Python should use sem_clockwait(CLOCK_MONOTONIC)

Mike Crowe added the comment: vstinner wrote: > The glibc 2.30 adds pthread_cond_clockwait() which could be used to use > CLOCK_MONOTONIC. But if pthread_cond_clockwait() is available (glibc > 2.30 or newer), it expects that pthread_condattr_setclock() is also > available. So I'm not sure

[issue41710] acquire(timeout) of threading.Lock and threading.Condition is affected by jumps in system time: Python should use sem_clockwait(CLOCK_MONOTONIC)

) from a relative timeout in microseconds. -- ___ Python tracker <https://bugs.python.org/issue41710> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue41710] acquire(timeout) of threading.Lock and threading.Condition is affected by jumps in system time: Python should use sem_clockwait(CLOCK_MONOTONIC)

Change by STINNER Victor : -- pull_requests: +27027 pull_request: https://github.com/python/cpython/pull/28662 ___ Python tracker ___

[issue41710] acquire(timeout) of threading.Lock and threading.Condition is affected by jumps in system time: Python should use sem_clockwait(CLOCK_MONOTONIC)

STINNER Victor added the comment: New changeset b34dd58fee707b8044beaf878962a6fa12b304dc by Victor Stinner in branch 'main': bpo-41710: Document _PyTime_t API in pytime.h (GH-28647) https://github.com/python/cpython/commit/b34dd58fee707b8044beaf878962a6fa12b304dc --

[issue41710] acquire(timeout) of threading.Lock and threading.Condition is affected by jumps in system time: Python should use sem_clockwait(CLOCK_MONOTONIC)

Change by STINNER Victor : -- pull_requests: +27015 pull_request: https://github.com/python/cpython/pull/28647 ___ Python tracker ___

[issue41710] acquire(timeout) of threading.Lock and threading.Condition is affected by jumps in system time: Python should use sem_clockwait(CLOCK_MONOTONIC)

STINNER Victor added the comment: New changeset 37b8294d6295ca12553fd7c98778be71d24f4b24 by Victor Stinner in branch 'main': bpo-41710: PyThread_acquire_lock_timed() clamps the timout (GH-28643) https://github.com/python/cpython/commit/37b8294d6295ca12553fd7c98778be71d24f4b24 --

[issue41710] acquire(timeout) of threading.Lock and threading.Condition is affected by jumps in system time: Python should use sem_clockwait(CLOCK_MONOTONIC)

STINNER Victor added the comment: New changeset 0231b6da45b610d33ee4e99bf190e31488d6ab26 by Victor Stinner in branch 'main': bpo-41710: Fix building pytime.c on Windows (GH-28644) https://github.com/python/cpython/commit/0231b6da45b610d33ee4e99bf190e31488d6ab26 --

[issue41710] acquire(timeout) of threading.Lock and threading.Condition is affected by jumps in system time: Python should use sem_clockwait(CLOCK_MONOTONIC)

Change by STINNER Victor : -- pull_requests: +27012 pull_request: https://github.com/python/cpython/pull/28644 ___ Python tracker ___

[issue41710] acquire(timeout) of threading.Lock and threading.Condition is affected by jumps in system time: Python should use sem_clockwait(CLOCK_MONOTONIC)

Change by STINNER Victor : -- pull_requests: +27011 pull_request: https://github.com/python/cpython/pull/28643 ___ Python tracker ___

[issue41710] acquire(timeout) of threading.Lock and threading.Condition is affected by jumps in system time: Python should use sem_clockwait(CLOCK_MONOTONIC)

STINNER Victor added the comment: New changeset d62d925823b005c33b432e527562b573a3a89635 by Victor Stinner in branch 'main': bpo-41710: Add pytime_add() and pytime_mul() (GH-28642) https://github.com/python/cpython/commit/d62d925823b005c33b432e527562b573a3a89635 --

[issue41710] acquire(timeout) of threading.Lock and threading.Condition is affected by jumps in system time: Python should use sem_clockwait(CLOCK_MONOTONIC)

Change by STINNER Victor : -- pull_requests: +27010 pull_request: https://github.com/python/cpython/pull/28642 ___ Python tracker ___

[issue41710] acquire(timeout) of threading.Lock and threading.Condition is affected by jumps in system time: Python should use sem_clockwait(CLOCK_MONOTONIC)

STINNER Victor added the comment: New changeset 09796f2f142fdb1214f34a3ca917959ecb32a88b by Victor Stinner in branch 'main': bpo-41710: Add _PyTime_AsTimespec_clamp() (GH-28629) https://github.com/python/cpython/commit/09796f2f142fdb1214f34a3ca917959ecb32a88b --

[issue41710] acquire(timeout) of threading.Lock and threading.Condition is affected by jumps in system time: Python should use sem_clockwait(CLOCK_MONOTONIC)

Change by STINNER Victor : -- keywords: +patch pull_requests: +26999 stage: -> patch review pull_request: https://github.com/python/cpython/pull/28629 ___ Python tracker ___

[issue27978] concurrent.futures.threading: Add a timeout to Executor shutdown() method

Change by STINNER Victor : -- title: [threading] Executor#shutdown with timeout -> concurrent.futures.threading: Add a timeout to Executor shutdown() method ___ Python tracker <https://bugs.python.org/issu

[issue41367] Popen Timeout raised on 3.6 but not on 3.8

Change by Irit Katriel : -- stage: -> resolved status: pending -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue45200] test_multiprocessing_fork: test_get() fails with timeout

STINNER Victor added the comment: > https://github.com/python/cpython/pull/28344/checks?check_run_id=3605759743 That's an Address Sanitizer job. Pablo: would it be possible to make the Address Sanitizer not mandatory on pull requests, until this libasan race condition is fixed? --

[issue45200] test_multiprocessing_fork: test_get() fails with timeout

STINNER Victor added the comment: When the test hangs, a background Python process starts to use 100% of my CPU. This process is stuck in _thread.start_new_thread(). I opened the process in gdb. (gdb) thread 1 [Switching to thread 1 (Thread 0x7fece33615c0 (LWP 132301))] #0

[issue45200] test_multiprocessing_fork: test_get() fails with timeout

STINNER Victor added the comment: > I'm able to reproduce the issue in a reliable way using attached bisect10 > file and the command: I'm talking about a Python built with Address Sanitizer: $ ./configure --with-address-sanitizer --without-pymalloc $ make --

[issue45200] test_multiprocessing_fork: test_get() fails with timeout

STINNER Victor added the comment: I'm able to reproduce the issue in a reliable way using attached bisect10 file and the command: $ ./python -m test test_multiprocessing_fork --timeout=40 -v --matchfile=bisect10 (...) test_fork (test.test_multiprocessing_fork.WithProcessesTestQueue) ... ok

[issue45200] test_multiprocessing_fork: test_get() fails with timeout

STINNER Victor added the comment: Sometimes, WithProcessesTestProcess.test_error_on_stdio_flush_1() hangs. -- ___ Python tracker ___

[issue45200] test_multiprocessing_fork failws with timeout

STINNER Victor added the comment: test_multiprocessing_fork also failed on the GitHub Action "Address sanitizer" job: https://github.com/python/cpython/pull/28419 test_get (test.test_multiprocessing_fork.WithProcessesTestQueue) ... Timeout (0:20:00)! Thread 0x7f732679bbc0 (m

[issue45200] test_multiprocessing_fork: test_get() fails with timeout

Change by STINNER Victor : -- title: test_multiprocessing_fork failws with timeout -> test_multiprocessing_fork: test_get() fails with timeout ___ Python tracker <https://bugs.python.org/issu

[issue45200] test_multiprocessing_fork failws with timeout

Change by Terry J. Reedy : -- keywords: +patch pull_requests: +26757 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/28344 ___ Python tracker

[issue45200] test_multiprocessing_fork failws with timeout

New submission from Terry J. Reedy : https://github.com/python/cpython/pull/28344/checks?check_run_id=3605759743 All tests pass until test_multiprocessing_fork timed out after 25 min. On the rerun: refail with timeout. test_get (test.test_multiprocessing_fork.WithProcessesTestQueue

[issue41710] acquire(timeout) of threading.Lock and threading.Condition is affected by jumps in system time: Python should use sem_clockwait(CLOCK_MONOTONIC)

Change by STINNER Victor : -- title: Timeout is affected by jumps in system time -> acquire(timeout) of threading.Lock and threading.Condition is affected by jumps in system time: Python should use sem_clockwait(CLOCK_MONOTONIC) ___ Python trac

[issue41367] Popen Timeout raised on 3.6 but not on 3.8

Irit Katriel added the comment: 3.6 is no longer maintained, so even if there was a bug in 3.6 that was fixed in 3.8 we aren't going to be able to do anything about it. If nobody objects I will close this issue soon. -- nosy: +iritkatriel resolution: -> out of date status: open ->

[issue41710] Timeout is affected by jumps in system time

Mike Crowe added the comment: glibc v2.30 onwards provides sem_clockwait which can wait on either CLOCK_MONOTONIC or CLOCK_REALTIME. I failed to notice that https://sourceware.org/bugzilla/show_bug.cgi?id=14717 existed until today. :( -- nosy: +mikecrowe

[issue8595] Explain the default timeout in http-client-related libraries

update; then it's easy to set the timeout when calling respective functions. -- ___ Python tracker <https://bugs.python.org/issue8595> ___ ___ Python-bugs-list mailin

[issue8595] Explain the default timeout in http-client-related libraries

Change by Andrei Kulakov : -- keywords: +patch nosy: +andrei.avk nosy_count: 6.0 -> 7.0 pull_requests: +25635 stage: -> patch review pull_request: https://github.com/python/cpython/pull/27087 ___ Python tracker

[issue43346] subprocess.run() sometimes ignores timeout in Windows

Change by Zachary Ware : -- nosy: +bugale bugale, eric.smith versions: +Python 3.11 ___ Python tracker ___ ___ Python-bugs-list

[issue29422] add socket independent timeout to httplib/http.client read

Change by Irit Katriel : -- versions: +Python 3.11 -Python 2.7, Python 3.3, Python 3.4, Python 3.5, Python 3.6, Python 3.7 ___ Python tracker ___

[issue36950] test.support: add an helper to wait for an event with a timeout

STINNER Victor added the comment: I close the issue because of the lack of activity. The need for this function is not very clear at this point. -- resolution: -> out of date stage: patch review -> resolved status: open -> closed ___ Python

[issue44204] socket.connect ignores CTRL+C during timeout on Win

New submission from Arpad Toth : Steps to Reproduce from http.client import HTTPConnection conn = HTTPConnection('192.1.5.2', 80, timeout=50) conn.request('GET', '/') conn.getresponse() Expected Behavior It should give up waiting when requested and exit immediately. Actual Behavior What

  1   2   3   4   5   6   7   8   9   10   >