propate no-match found nil
file after find* channel based queries
#537
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #536.
Updates #528.
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
// 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