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.

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

ping: Suppress ProcessLookupError on timeout #134281

Open
wants to merge 2 commits into
base: dev
Choose a base branch
from

Conversation

tswsl1989
Copy link

@tswsl1989 tswsl1989 commented Dec 30, 2024

Proposed change

Suppress log messages when the ping command exits after the timeout is reached.

If the ping command reaches the timeout while Home Assistant is waiting for data, the command is killed as part of the clean up. In some cases, the command can apparently exit before the clean up code is reached, causing an additional unhandled error to occur.

Suppressing this specific exception prevents the extra error messages being emitted, and allows the remainder of the exception handling to proceed.

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New integration (thank you!)
  • New feature (which adds functionality to an existing integration)
  • Deprecation (breaking change to happen in the future)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Additional information

Checklist

  • The code change is tested and works locally.
  • Local tests pass. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • I have followed the development checklist
  • I have followed the perfect PR recommendations
  • The code has been formatted using Ruff (ruff format homeassistant tests)
  • Tests have been added to verify that the new code works.
    • I'm not sure how to add a test for this case

If user exposed functionality or configuration variables are added/changed:

If the code communicates with devices, web services, or third-party tools:

  • The manifest file has all fields filled out correctly.
    Updated and included derived files by running: python3 -m script.hassfest.
    • Not applicable
  • New or updated dependencies have been added to requirements_all.txt.
    Updated by running python3 -m script.gen_requirements_all.
    • Not applicable
  • For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
    • Not applicable

To help with the load of incoming pull requests:

Copy link

@home-assistant home-assistant bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @tswsl1989

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

@home-assistant
Copy link

Hey there @jpbede, mind taking a look at this pull request as it has been labeled with an integration (ping) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of ping can trigger bot actions by commenting:

  • @home-assistant close Closes the pull request.
  • @home-assistant rename Awesome new title Renames the pull request.
  • @home-assistant reopen Reopen the pull request.
  • @home-assistant unassign ping Removes the current integration label and assignees on the pull request, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

@bdraco
Copy link
Member

bdraco commented Dec 31, 2024

The change looks good. Would you please add a test to cover this case?

@tswsl1989
Copy link
Author

I've added what I think are a pair of sensible tests for this, although I couldn't find similar examples in the tests folder. Let me know if you think there's a better approach.

When using the ping command, the command is killed if the timeout limit
is reached before output is returned. If the ping process has exited
before the exception is handled, a ProcessLookupError is raised.
This generates exceptions in the log, but adds no useful information.

As the command is being killed here to ensure it's terminated as part of
error handling, suppress the exception raised in this instance to reduce
noise in the application log.
Tests that expected exceptions are handled, but unexpected exceptions
are still raised.

Patches out asyncio.create_subprocess_exec to generate exceptions, which
also means that the external ping command is not called during these
tests.
@bdraco
Copy link
Member

bdraco commented Jan 7, 2025

Normally we would want an end to end test, but thats likely not possible here because you are mocking a race condition. So I think its fine to test the helper directly in this case

raise self.killsig


async def test_async_ping_expected_exceptions(
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd use pytest.mark.parametrize to test TypeError as well

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants