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.

Sign up for GitHub

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

Jump to bottom

Fail-safe for unparsable /proc entries #10

Closed
uranusjr opened this issue Sep 5, 2018 · 0 comments
Closed

Fail-safe for unparsable /proc entries #10

uranusjr opened this issue Sep 5, 2018 · 0 comments
Labels
enhancement New feature or request

Comments

@uranusjr
Copy link
Member

uranusjr commented Sep 5, 2018

From pypa/pipenv#2820. Currently the detection explodes if cmdline (or any other proc entries) is faulty. While there is no way to solve the decode error (it is entirely machine-dependant), Shellingham can at least try to ignore the file and continue looking, hoping that faulty file is not the one we’re looking for.
@uranusjr uranusjr added the enhancement New feature or request label Sep 5, 2018
@uranusjr uranusjr mentioned this issue Dec 15, 2018
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@uranusjr