-
Notifications
You must be signed in to change notification settings - Fork 234
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
Error at the end of the build #473
Comments
Thanks for reporting. I can fix this based on your input, and using a Fedora image. I can't replicate it locally, but probably because my process id is already so high that no space is output. Edit: the error was introduced by me, here. |
@andrei-mihaila, I've pull requested to fix this. Would you care to check the proposed changes and let us know if they're effective for your use case: https://github.com/kerl/kerl/pull/474/files? Thanks. Ah, as a side note: I could just go back to the "old" code and add the |
Tested and it works. Thank you! |
The bug
Getting an error at the end of the build:
This probably just affects the message displayed at the end of the build ('You can activate this installation running the following command:') - not displayed.
Software versions
A list of software versions where the bug is apparent, as detailed as possible:
kerl
: latest, retrieved on 2023.10.05 from https://raw.githubusercontent.com/kerl/kerl/master/kerlps from procps-ng 4.0.4
How to replicate
An ordered list of steps to replicate the bug, e.g.:
kerl build ...
error: improper list
in the error outputExpected behaviour
The error should not be happening and the right message should be displayed at the end of the build.
Additional context
I think the problem is on this line: 1462.
The code is running
ps
to get the parent PID (used later to determine if the current terminal is bash or zsh or other). The result of that line can contain leading spaces, for example:$ ps -p $$ -o ppid= 2970
On the next line ps expects a list of comma separated PIDs (no spaces). For example:
Thanks!
The text was updated successfully, but these errors were encountered: