-
Notifications
You must be signed in to change notification settings - Fork 67
say which file failed #246
Comments
ah.. the version:
|
That's a good point. I wonder if all error messages should say the name of the file. At least, all error messages that say there's something wrong with the file, as opposed to users doing something they shouldn't. |
here the message is very clear as what's wrong in the file, my only wish is to find that file ! |
Take a look at that diff: every error message that pertains to a file-formatting error now prints out the name of the file. I hope I haven't added any errors-during-error-handling, since those can be frustrating and they're not well tested (error conditions generally don't get the coverage that features do). But it looks like I dotted all my 'i's. |
after looking I can only be humbled by how quickly you get things done. I am of the kind "one line, two typos", do not count on me to find the t's you didn't cross :-) thanks. |
when using numentries with a list of URL's I have hit this exception [1]
The lines before the stacktrace come from my script and say that it is trying to
get entries from all root files in
/eos/uscms/store/group/lpcbacon/15/JetHTRun2016H_07Aug17_v1_ddb8X
and there are 4308 of them.
I call root files all whose name end in .root and rely on uprood after that
(a usual situation, I am sure).
I 'd like the expection message to print the name of the bad file,
so that proper actions can be taken.
I cant' say if it is reproducible or if it was an xrootd server glitch.
[1]
The text was updated successfully, but these errors were encountered: