Prevent exception while running BorgVersionJob with unexpected lines on stderr

[ntninja]

Description

The borg job logic expects the profile_name key to be unconditionally present in the params if any data is received on stderr. This causes the BorgVersionJob (which didn’t set this param) to fail if any unexpected output – such as LD_PRELOAD warnings – in generated while running borg --version. This in turn causes Vorta to silently (other than an unrelated looking exception in the console output) fall back to assuming borg 1.1.0 as the borg version.

Related Issue

Please don’t make me create an issue for this…

Motivation and Context

Borg version detection currently silently fails in environments that have LD_PRELOAD set in a way to causes warnings to be emitted.

How Has This Been Tested?

The change is pretty trivial, so I just tested with and without.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• I have read the CONTRIBUTING guide.
• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

I provide my contribution under the terms of the license of this repository and I affirm the Developer Certificate of Origin.

[real-yfprojects]

Thank you for taking the time to create this PR. You can find my commentary below.

[m3nu]

Was also looking at this. Currently wondering about the test timeouts on Linux. A Github glitch?

[real-yfprojects]

A Github glitch?

Not sure what it is, but the line collecting ... collected 166 items was already produced 13min 4min in. So either it was idling for 7 minutes or there is a step in pytest that took this long and doesn't produce any output.