Closed joshmoore closed 4 years ago
Thanks, @joshmoore. @kkoz is working on a variety of scenarios surrounding this. We were unable to find anything other than broken imports where size
was null
but there were also lots of other conditions that we found were the error checking was sub par. I'll let him comment when he's ready.
:+1: Also feel free to just open separately and I can close this. Right now I'm looking into what the behavior is when one accidentally tries to download a Directory
or a Repository
. If you know what the original target was (called 123456
above) that would be useful.
Yep, those are exactly conditions we were seeing as well. Also seen with trying to download an OMERO.tables instance. The original 123456
target was what we could only assume to be a broken import from many years ago. File was not actually in the ManagedRepository
and the OriginalFile instance only partially filled out. The reason it was selected was misunderstanding the documentation and assuming 123456
was an Image ID (requiring Image:123456
as a command line option) rather than an OriginalFile ID.
Minor update to hide the stack trace from the user, e.g.:
ClientError: invalid size for OriginalFile 'Meas_04(2011-02-22_19-24-25)' (mimetype:Directory)
--exclude
If an unexpected download ID is given, the client can fail with:
(line numbers are from 5.4.10)
cc: @chris-allan