Improve LockError message

[algomaster99]

• ❗ Have you followed the guidelines in the Contributing to DVC list?

• 📖 Check this box if this PR does not require documentation updates, or if it does and you have created a separate PR in dvc.org with such updates (or at least opened an issue about it in that repo). Please link below to your PR (or issue) in the dvc.org repo.

• ❌ Have you checked DeepSource, CodeClimate, and other sanity checks below? We consider their findings recommendatory and don't expect everything to be addresses. Please review them carefully and fix those that actually improve code or fix bugs.

Thank you for the contribution - we'll try to review it as soon as possible. 🙏

Fixes #2520

Changed error message

[algomaster99]

@efiop @Suor @MrOutis
Let's decide how the error message should be then I will fix the codeclimate issue by assigning the message to a variable. 😄

[jorgeorpinel]

Better language suggestion:

[pared]

Use upper case name (DVC vs dvc)

[jorgeorpinel]

Hmmm. He uses "DVC" first, but the 2nd time I think he's referring to the dvc process. Should wrap it in back ticks ` though.

[Suor]

I would rephrase it. The but-clause makes it harder to read than needed. Also "busy and locked" is too abstract, what does it mean? And cmd -> command.

So, it's like:

Cannot perform the command since other dvc process is running for this repo. If you are sure this is not the case, you might remove .dvc/lock to fix this ...

Then command line hints go. However, ps xaf | grep dvc doesn't make sense for Windows, unless again they don't use bash or somehting there.

[shcheklein]

👍 , I agreed wtih @Suor regarding rephrasing. Also, including command line hints to check running processes I think is way too much. Let's just remove this part completely.

[pared]

One little change, and one thing to consider.
Also, do you, by any chance, have a way to trigger this message? Maybe some script that could be shown through ascinema?

EDIT: sorry, didn't notice the print screen

[Suor]

I would rephrase it. The but-clause makes it harder to read than needed. Also "busy and locked" is too abstract, what does it mean? And cmd -> command.

So, it's like:

Cannot perform the command since other dvc process is running for this repo. If you are sure this is not the case, you might remove .dvc/lock to fix this ...

Then command line hints go. However, ps xaf | grep dvc doesn't make sense for Windows, unless again they don't use bash or somehting there.

[Suor]

If this is about an error message only then why do we change the return code?

[algomaster99]

@efiop might be able to answer this.

[algomaster99]

@Suor What will be the command on cmd on Windows? tasklist | findstr dvc?

[efiop]

LockError is based on DvcException and doesn't make it up here, as all CLI commands have try except DvcException in them. So we can remove this bit.

[algomaster99]

Updated message

[shcheklein]

@algomaster99 looks good to me!

I have though some concerns (probably it's better to address them to @jorgeorpinel, @efiop ) about back-ticks . I think it's not a common practice to use markdown markup in UI.

[jorgeorpinel]

Please just update dvc -> DVC per #2765 (comment). Thanks

[algomaster99]

@jorgeorpinel Capitalized dvc (DVC) shouldn't be enclosed in back-ticks, right?

[jorgeorpinel]

No back ticks, thanks!

[pared]

LGTM 🚀