Allow listdir in /proc in the event loop #120969
Conversation
![home-assistant[bot]](https://avatars.githubusercontent.com/in/97978?s=60&v=4){kind=small}
There was a problem hiding this comment.
Hello @knyar,
When attempting to inspect the commits of your pull request for CLA signature status among all authors we encountered commit(s) which were not linked to a GitHub account, thus not allowing us to determine their status(es).
The commits that are missing a linked GitHub account are the following:
b642bef0ab24421fdb4d191a44a1441f16b7161b- This commit has something that looks like an email address (ryzh@cossacklabs.com). Maybe try linking that to GitHub?.
Unfortunately, we are unable to accept this pull request until this situation is corrected.
Here are your options:
-
If you had an email address set for the commit that simply wasn't linked to your GitHub account you can link that email now and it will retroactively apply to your commits. The simplest way to do this is to click the link to one of the above commits and look for a blue question mark in a blue circle in the top left. Hovering over that bubble will show you what email address you used. Clicking on that button will take you to your email address settings on GitHub. Just add the email address on that page and you're all set. GitHub has more information about this option in their help center.
-
If you didn't use an email address at all, it was an invalid email, or it's one you can't link to your GitHub, you will need to change the authorship information of the commit and your global Git settings so this doesn't happen again going forward. GitHub provides some great instructions on how to change your authorship information in their help center.
- If you only made a single commit you should be able to run
(substituting "Author Name" and "
git commit --amend --author="Author Name <email@address.com>"email@address.com" for your actual information) to set the authorship information. - If you made more than one commit and the commit with the missing authorship information is not the most recent one you have two options:
- You can re-create all commits missing authorship information. This is going to be the easiest solution for developers that aren't extremely confident in their Git and command line skills.
- You can use this script that GitHub provides to rewrite history. Please note: this should be used only if you are very confident in your abilities and understand its impacts.
- Whichever method you choose, I will come by to re-check the pull request once you push the fixes to this branch.
- If you only made a single commit you should be able to run
We apologize for this inconvenience, especially since it usually bites new contributors to Home Assistant. We hope you understand the need for us to protect ourselves and the great community we all have built legally. The best thing to come out of this is that you only need to fix this once and it benefits the entire Home Assistant and GitHub community.
Thanks, I look forward to checking this PR again soon! ❤️
|
Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍 |
|
cc @bdraco |
|
I’m not sure if listdir on /proc/self/fd can block or not. We need to look at the kernel sources to see if it’s safe to exclude or not |
|
Digging though https://elixir.bootlin.com/linux/v5.19.4/source/fs/proc, it does look like listing /proc/self/fd can block as there are quite a few places it can lock so that lookup should run in the executor The other use cases we allow are are mainly for reading cpu/memory stats which doesn't appear to block https://elixir.bootlin.com/linux/v5.19.4/source/fs/proc/stat.c. That exclude should be more narrow but that's another issue |
|
Thank you for the quick response here! Closing this in favor of #121058. |
Proposed change
It seems like there's some automation now that detects blocking IO in Home Assistant, and I've been looking at #120778 which reported an
os.listdir()call made by the metric library that theprometheusintegration uses.Taking a closer look in
block_async_io, it seems like some operations in/prochave been deemed acceptable, so perhaps the right change here is to extend that exception list toos.listdir?Please let me know if I misunderstood the intent here - I am happy to move the blocking code to be ran by the executor as suggested in developer docs.
Type of change
Additional information
Checklist
ruff format homeassistant tests)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest.requirements_all.txt.Updated by running
python3 -m script.gen_requirements_all..coveragerc.To help with the load of incoming pull requests: