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
This bug was reported by @memeplex in the interaction in issue #535. I reproduced and acknowledged it in #535 (comment).
It is an offset of PR #528, caused by the new pattern remote.FindByPathM -- multiple which returns a channel. Originally a call
files, err:=req.Do()
iferr!=nil {
iferr.Error() ==ErrGoogleApiInvalidQueryHardCoded.Error() { // Send the user back the query informationerr=fmt.Errorf("err: %v query: `%s`", err, expr)
}
returnnil, err
}
iffiles==nil||len(files.Items) <1 {
returnnil, ErrPathNotExists
}
first:=files.Items[0]
iflen(p) ==1 {
returnNewRemoteFile(first), nil
}
returnr.findByPathRecvRaw(first.Id, p[1:], trashed)
The original pattern guaranteed the reporting of unmatched files
and yet now
orrem:=rangeremotesChan {
....
}
// Will never be run if the file didn't exist upstream.
yet at no point was a lack of the first match ever propagated back with the empty file
The text was updated successfully, but these errors were encountered:
This bug was reported by @memeplex in the interaction in issue #535. I reproduced and acknowledged it in #535 (comment).
It is an offset of PR #528, caused by the new pattern remote.FindByPathM -- multiple which returns a channel. Originally a call
The original pattern guaranteed the reporting of unmatched files
and yet now
yet at no point was a lack of the first match ever propagated back with the empty file
The text was updated successfully, but these errors were encountered: