attempt to handle rose rsync can_pull errors better#2892
Conversation
|
Did you manage to work out why the command stderr was not logged? |
Because no one made Rose log it. When I was testing it in front of you and there was no output, that was because On consideration, I should probably have a specific error message for this outcome! |
I would expect there to be some standard way of doing this (else we would have to do this for every single command individually). From a quick code skim, it looks like this is the centralised logic: Lines 44 to 61 in 26a6066 So, I think the issue here, is that this command swallows the |
54fa62e to
6609cfb
Compare
4b72a72 to
52e10d5
Compare
ff9dba2 to
29067ef
Compare
handle no file error with useful error message Apply suggestions from code review Co-authored-by: Ronnie Dutta <61982285+MetRonnie@users.noreply.github.com> Response to review move error messaging into error class
c1f1a7a to
a9eac4a
Compare
|
@oliver-sanders Poke |
|
You may want to consider changing to a bugfix branch. Plz squash merge. |
Fixes problem not recorded in an issue:
Issue
Rose has a routine to work out which
file_loc_handlershould be used based on the content of thesource=field. However, the function called by thersyncloc handler will attempt to runAs part of the method used to decide if the source is an Rsync handler. This fails in a difficult to debug way, as it's unclear whether the rsync check routine failed because the host was unreachable, or the file didn't exist, or the
sourcewas not meant to be a location reached byrsync, or was just garbage.This PR