Flow: say so when a pinned subrepo is left out for lack of access issue #56
closed: completed andymccall opened this · 0 comments
andymccall
A Flow job gets a pinned subrepo only when the run's actor can read it (subrepo_inputs). When they cannot (a private subrepo, or a run started by a token without an account), the subrepo is silently left out and the job fails later with missing files. The claim should instead fail the job with 'subrepo PATH (OWNER/NAME) is not readable by ACTOR', or at least log it in the job's log.
A Flow job gets a pinned subrepo only when the run's actor can read it (subrepo_inputs). When they cannot (a private subrepo, or a run started by a token without an account), the subrepo is silently left out and the job fails later with missing files. The claim should instead fail the job with 'subrepo PATH (OWNER/NAME) is not readable by ACTOR', or at least log it in the job's log.