Custom Query (2425 matches)

Opening an i3file with a fresh build of combo.trunk (r178839) using py3-v4.0.1 results in a Segmentation fault:

************************************************************************
*                                                                      *
*                   W E L C O M E  to  I C E T R A Y                   *
*                                                                      *
*                   Version combo.trunk     r178839                    *
*                                                                      *
*                You are welcome to visit our Web site                 *
*                        http://icecube.umd.edu                        *
*                                                                      *
************************************************************************

Icetray environment has:
   I3_SRC       = /scratch/eganster/software/meta-projects/combo/trunk/src
   I3_BUILD     = /scratch/eganster/software/meta-projects/combo/trunk/build_py3-v4.0.1
   I3_TESTDATA  = /cvmfs/icecube.opensciencegrid.org/py3-v4.0.1/../data/i3-test-data-svn/trunk
   Python       = 3.6.8

eganster@cobalt03 ~ $ dataio-shovel /cvmfs/icecube.opensciencegrid.org/data/GCD/GeoCalibDetectorStatus_AVG_55697-57531_PASS2_SPE_withScaledNoise.i3.gz
Segmentation fault

I3::data::open's compression type detection has gotten too clever by half. Instead of using gz/bz2/zst filters if a file name ends with the corresponding extension, it requires that the file end in .i3.gz, .i3.bz2, .i3.zst, etc. This breaks file staging, which uses os.path.splitext() to preserve only the primary file extension, e.g. mapping gsiftp://gridftp.icecube.wisc.edu/data/sim/IceCube/2016/filtered/level2/neutrino-generator/21002/0004000-0004999/Level2_IC86.2016_NuMu.021002.004215.i3.zst to /mnt/glidein/execute.172.16.142.76-73/dir_1739/tmpxA7B47/Level2_IC86.2016_NuMu.021002.004215.i3_000000.zst. Files opened for writing don't have this restriction.

see title