-
Notifications
You must be signed in to change notification settings - Fork 501
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
missing input read files do not throw errors and arguably should #843
Comments
Good suggestion - thanks, Malcolm! |
Hi Malcolm I have pushed a patch into master that fixes this problem, please check it out. There will be an official 2.7.3b release in the next few days. Cheers |
Finally testing now with version 2.7.9a, I still find that STAR does not raise an error when a file named in readFilesIn does not exist, and does not (at least in combination with ;( |
Hi Malcolm, thanks for bumping it, will implement this check in the next release. Cheers |
STAR would benefit from catching and raising an error if reading from the input read filesitself raises an error.
At least in one case it does not, namely when
--readFilesCommand zcat -f
and the--readFilesIn f1,f2,f3
do not exist.The Log shows it as follows:
Certainly the system call to
ls
raising an error.If STAR would itself throw an error in such cases, it would improve the user experience in using it.
The text was updated successfully, but these errors were encountered: