-
Notifications
You must be signed in to change notification settings - Fork 5
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
Printing the command being run when encountering an error. #32
Comments
The log /should does print the command being run. For example, I recently had one terminate with:
The problem is --- WTH is |
Right, I also got weird error messages like this. Is there a way to copy and paste the error message returned by salmon and alevin-fry when quitting with errors? |
It depends how they report the error, they may not report a message. The standard way to do this would be to capture the standard error buffer and dump that as well. However, these errors (e.g. wait status 512) are usually due to missing files. From that perspective, I think defensive checks for files being where the user expected they were would cover like 80% of the problems. |
Basic input file checking has been implemented as of 034d531. It can still be improved (e.g. to make sure that things expected to be files are files and things expected to be directories are directories). Also, we can (if we choose) explicitly check for the expected files inside of directory arguments. However, I'll consider what we currently have to be a decent solution, or at least the start of one. |
One suggestion: when running simpleaf, if we encounter an error, can we print the command being run? I had some path issues when running simpleaf quant. It just told me that mapping failed. To debug it, I had to go to
quant_info.json
and find the mapping command and remove all quotes between arguments and run thesalmon alevin
command.The text was updated successfully, but these errors were encountered: