xybu
commented
9 years ago For an in-development program, what is more important is to know what the program has been doing in case any bug happens. This makes it easier to analyze the causes of problems when one shares the log with me. I am aware that currently there are more than necessary print statements. When the app is mature enough the log level will be raised and there will be much less log content.
Sincerely, Xiangyu Bu
Sent from my Windows Phone
From: Craig Denmanmailto:notifications@github.com Sent: 11/24/2014 10:30 PM To: xybu/onedrive-dmailto:onedrive-d@noreply.github.com Subject: [onedrive-d] Verbose messaging and terminal trace back info (#92)
I have just started using onedrive-d and completed my Ubuntu 10GB backup a couple of days ago. Since then, I have onedrive-d startup during the boot. It appears to be working and I can identify with some of the issues listed by others. I thought that after the first two days that the backup sync to OneDrive had completed, but each day there is a lot of network traffic 500kB or more that will go for hours including the messaging -- and I have not changed anything. I look at my terminal to see what state the backup is in and there is no information that I can decifer. I use Unison with Box.com where a similar manual sync process is involved, but in this case, Unison provides a short and succinct message that is easy to interpret. I understand that the development of onedrive-d is in its earliest stages, but I just wanted to suggest how important clear messaging is to the end user -- I don't know when it has started, what state it is in, or if any errors have occured, or when it has completed. A log is a better place for more verbose reports -- but always I must be able to figure out what it all means, in case there is an error caused by something that I did. Thanks for the great work that you have done to provide onedrive-d.
Reply to this email directly or view it on GitHub: https://github.com/xybu/onedrive-d/issues/92
CraigAD
I have just started using onedrive-d and completed my Ubuntu 10GB backup a couple of days ago. Since then, I have onedrive-d startup during the boot. It appears to be working and I can identify with some of the issues listed by others. I thought that after the first two days that the backup sync to OneDrive had completed, but each day there is a lot of network traffic 500kB or more that will go for hours including the messaging -- and I have not changed anything. I look at my terminal to see what state the backup is in and there is no information that I can decifer. I use Unison with Box.com where a similar manual sync process is involved, but in this case, Unison provides a short and succinct message that is easy to interpret. I understand that the development of onedrive-d is in its earliest stages, but I just wanted to suggest how important clear messaging is to the end user -- I don't know when it has started, what state it is in, or if any errors have occured, or when it has completed. A log is a better place for more verbose reports -- but always I must be able to figure out what it all means, in case there is an error caused by something that I did. Thanks for the great work that you have done to provide onedrive-d.