Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

It is hard to detect a user error externally for pcsync rename since the return code is 0 #41

Open
querielo opened this issue Jul 5, 2022 · 0 comments
Open

It is hard to detect a user error externally for pcsync rename since the return code is 0 #41

querielo opened this issue Jul 5, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@querielo
Copy link
Contributor

querielo commented Jul 5, 2022 •
edited
Loading

It is hard to detect if a pcsync command is done since wrapUserErrors does not cause the program returns non-zero code.

For example, pcsync rename lalalilolu.txt lalelilolu.txt always returns 0 even if lalalilolu.txt does not exist. And you have to parse stdout to detect the issue.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@willeastcott @zachpeterpaul @querielo