Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Add handle_signals option to llfuse.main #15

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

Merged
merged 3 commits into from
Jul 9, 2018

Conversation

touilleMan
Copy link
Contributor

The other point discussed in #13
Regarding how to test this, I'm not sure using test_fs.py would be great given this would mean modify run_fs (given it's were llfuse.main is called) and add some test related code there too (typically installing a custom signal handler)...

src/fuse_api.pxi Outdated
While this function is running, special signal handlers will be installed
for the *SIGTERM*, *SIGINT* (Ctrl-C), *SIGHUP*, *SIGUSR1* and *SIGPIPE*
signals. *SIGPIPE* will be ignored, while the other three signals will cause
*handle_signals* specifies if special signal handlers should be installed
Copy link
Contributor

Choose a reason for hiding this comment

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

That's very hard to read (runaway sentence). Can you just prefix the existing docstring with "Unless handle_signals is False, while this function is running [...]"?

@Nikratio
Copy link
Contributor

Nikratio commented Jul 9, 2018

Looks good. I agree, there is no way to test this with reasonable effort. Could you improve the docstring and add an entry to ChangeLog.rst?

@touilleMan
Copy link
Contributor Author

@Nikratio I've updated the PR 👍

@Nikratio
Copy link
Contributor

Nikratio commented Jul 9, 2018

Thanks!

@Nikratio Nikratio merged commit a9fa8dd into python-llfuse:master Jul 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants