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.

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

Properly propagate transfer issues #432

Open
JoeZiminski opened this issue Sep 26, 2024 · 0 comments
Open

Properly propagate transfer issues #432

JoeZiminski opened this issue Sep 26, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@JoeZiminski
Copy link
Member

At the moment the transfer occurs on the rclone side and the user has to go and check the logs to see whether the transfer completely properlly. It would be much better to check the rlcone side (hopefully it can be made to return a code based on issues encountered in the error (nice)) or search the log file for any errors and propagate to the user (not nice). For example, it is currently confusing if the transfer fails due to a bad central path over SSH.

@JoeZiminski JoeZiminski added the enhancement New feature or request label Sep 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant