[obspy-users] Miniseed file accidentally recognised as tar
krischer at geophysik.uni-muenchen.de
Wed Jun 1 19:29:37 CEST 2016
Can we use the file as part of a regression test in ObsPy? e.g. it will
then be included in ObsPy to make sure this never happens again.
On 01/06/16 15:52, Roman Racine wrote:
> Hi Lion,
> oops, I have attached the wrong file. I have attached the miniseed file
> Kind regards
> On 06/01/2016 03:47 PM, Lion Krischer wrote:
>> Hi Roman,
>> can you send us the actual file as well or open an issue on Github?
>> It is a bit strange as all files that are opened with ObsPy go through
>> that decorator and don't get false positives for the tarfile detection.
>> So we either have to improve the detection or something else is wrong.
>> On 01/06/16 15:21, Roman Racine wrote:
>>> Hi all,
>>> I have attached a small miniseed file which cannot be read by obspy.
>>> After some debugging, I found out that the problem lies in
>>> It has a function "uncompress_file" which serves as a decorator to _read
>>> in stream.py. Obviously, the file is recognised as tar and treated as
>>> such despite the fact that it is not. I suppose a simple test whether
>>> any data was read successfully from the tar file would prevent this
>>> Kind reagards
>>> Roman Racine
>>> obspy-users mailing list
>>> obspy-users at lists.swapbytes.de
>> obspy-users mailing list
>> obspy-users at lists.swapbytes.de
> obspy-users mailing list
> obspy-users at lists.swapbytes.de
More information about the obspy-users