During commit, the vyos backend intercepts and prepends the stdout stream with diagnostic information in case of error; any subsequent write to stdout during commit will carry the path as part of the prepend message, even in the absence of error.
This is not new behaviour, but had been minimally disruptive until replacing os.system with vyos.util.call in many scripts; vyos.util.call will print to stdout even in the case of empty output, and hence will always carry the prepend_msg.
The backend logic of adding the path to the prepend message, even in the absence of error, appears to be incorrect and will be evaluated here to see if the benefits of changing it outweigh possible complications.
The Python function vyos.util.call will be changed to only print non-empty output, as is reasonable, but will have the effect of suppressing the output of the path on (many) script invocations.