| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Sorry, something went wrong.
|
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool. If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead. |
Sorry, something went wrong.
|
Thank you for the PR. Would you mind updating the documentation, adding a NEWS entry using the blurb tool and signing the CLA? Thanks again. |
Sorry, something went wrong.
|
Thanks for those. You don't feel comfortable updating the docs? |
Sorry, something went wrong.
|
@vsajip Oh, I thought you meant only the blurb. I'll update the documentation as well |
Sorry, something went wrong.
Hopefully the first of many contributions! As it's an API change, it needs the documentation updating so users will know about the new parameter. |
Sorry, something went wrong.
| @@ -0,0 +1,3 @@ | |||
| Added a timeout parameter to logging.handlers.SysLogHandler class to control the TCP socket timeout and prevent process blocking when the Syslog server is unreachable; this improves resilience when working with unresponsive Syslog servers. | |||
There was a problem hiding this comment.
| Added a timeout parameter to logging.handlers.SysLogHandler class to control the TCP socket timeout and prevent process blocking when the Syslog server is unreachable; this improves resilience when working with unresponsive Syslog servers. | |
| Added a timeout parameter to :class:`logging.handlers.SysLogHandler` class to control the TCP socket timeout and prevent process blocking when the Syslog server is unreachable; this improves resilience when working with unresponsive Syslog servers. | |
Sorry, something went wrong.
There was a problem hiding this comment.
Please update file ./Doc/library/logging.handlers.rst to mention added timeout parameter.
Take a look atsocktype argument for inspiration.
Sorry, something went wrong.
|
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase I have made the requested changes; please review again. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request. |
Sorry, something went wrong.
|
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool. If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead. |
Sorry, something went wrong.
|
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool. If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead. |
Sorry, something went wrong.
|
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool. If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead. |
Sorry, something went wrong.
|
The docs build is failing with some unrelated error in processing the Misc/NEWS entries, same happens locally. I've fixed the sphinx lint error and missing blurb in this PR. Not sure what the docs build problem is. |
Sorry, something went wrong.
|
Somewhere, perhaps during a force-push, the original blurb got lost. I added a new one (a bit shorter) and everything now seems to be building correctly. I had to update a couple of unrelated blurb files, seemingly because they wrongly had gh: instead of gh-issue: in places (perhaps a change to blurb caused the build failures). |
Sorry, something went wrong.
…locking (pythonGH-126716) Co-authored-by: Vinay Sajip <vinay_sajip@yahoo.co.uk>
| Back | FazBrowse Home | New Git URL |
Issue #126400.
branch name - fix-issue-126400
Summary
In the current implementation of the SysLogHandler class from the logging.handlers module, if the specified address does not respond or is unreachable, the createSocket method may block indefinitely in case of using TCP socket (based on stream). This is problematic because there is no way to set a socket timeout during the connection's creation without overriding the entire createSocket method.
Changes
This change allows users to prevent indefinite blocking on socket creation, enabling more robust error handling when the SysLog server is unresponsive.
Example Usage
With this update, users can now create a SysLogHandler with a timeout as follows: