You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We recently had a report that the pipeline wasn't working:
!! Error reading file names from stream attached to shell process -
! Interrupted system call
!! No files found matching the file specification
! '/Users/person/Oph_H2D+/cube_recipe/adam_61767/ndfpack_mon'.
!! HDS_OPEN: Error opening an HDS container file.
The problem was that HDS was entering the wildcard match part of the code and failing to find the file. The culprit here being the + in the directory name. It's not clear whether this is fixable without a lot of work (splitting the path up and checking each component in turn to see if it exists) but I'm logging this for reference.
It also made clear to me that HDS is still forking processes to look for wildcard files (and rec1_find_file dynamically creates a shell script) rather than using wordexp() like the rest of Starlink.
The text was updated successfully, but these errors were encountered:
We recently had a report that the pipeline wasn't working:
The problem was that HDS was entering the wildcard match part of the code and failing to find the file. The culprit here being the
+
in the directory name. It's not clear whether this is fixable without a lot of work (splitting the path up and checking each component in turn to see if it exists) but I'm logging this for reference.It also made clear to me that HDS is still forking processes to look for wildcard files (and
rec1_find_file
dynamically creates a shell script) rather than usingwordexp()
like the rest of Starlink.The text was updated successfully, but these errors were encountered: