Doesn't work for large folders

Question

Doesn't work for large folders

iliakan opened this issue 8 years ago · 9 comments

iliakan commented 8 years ago

I installed it and run to download a large folder.

After a short time I started to get "Response returned with status code 401" errors, guess token expired or something.

Answer 1 · 2016-06-09T12:07:57.000Z

Were any files able to successfully download? There is a retry mechanism already built-in.

Answer 2 · 2016-06-09T12:11:17.000Z

Also what is the output when you run the init command.

Answer 3 · 2016-06-11T07:27:21.000Z

Yeah, things were working fine until I started to get 401s.

Answer 4 · 2016-06-11T07:27:41.000Z

init command was fine.
Sorry for not answering immediately, I just didn't think the project is well-supported.

Answer 5 · 2016-06-14T00:27:57.000Z

I've added a bunch of updates - could you pull down the master branch and see if that solves your issue?

Answer 6 · 2016-06-16T13:37:02.000Z

Now I tried to download the files one-by-one, like this clouddrive download -vvv $file.

And here's the issue.

I have in config:

cli.colors           = false
cli.progressBars     = false
cli.progressInterval = true

Now, the progress bar is not seen. BUT when I redirect the output to a log-file, I have a bunch of extra "progress" lines. It's hard to read the log file.

The lines are like this (using less for visible esc codes):

ESC[?25lDownloading webpack-screencast.tgz.aes.part07.rar
ESC[?25lESC[1000DESC[KESC[1AESC[1000DESC[KDownloading webpack-screencast.tgz.aes.part07.rar
ESC[?25lESC[1000DESC[KESC[1AESC[1000DESC[KDownloading webpack-screencast.tgz.aes.part07.rar
ESC[?25lESC[1000DESC[KESC[1AESC[1000DESC[KDownloading webpack-screencast.tgz.aes.part07.rar
ESC[?25lESC[1000DESC[KESC[1AESC[1000DESC[KDownloading webpack-screencast.tgz.aes.part07.rar
ESC[?25lESC[1000DESC[KESC[1AESC[1000DESC[KDownloading webpack-screencast.tgz.aes.part07.rar

The download breaks sometimes. The clouddrive exits with exit code 137 or 1 and no other messages. I don't know what to think.

Answer 7 · 2016-11-15T23:18:54.000Z

@iliakan I've added significantly more verbose logging (and support for logging to a file). I've never encountered the error your describing, but I'd like to get to the bottom of it. Pull down master and let me know if you have the same issue and attach the logs if you do.

Answer 8 · 2016-12-31T17:18:24.000Z

Closing the issue. If you can provide any more information, I can look into this, but I haven't been able to replicate it.

Answer 9 · 2016-12-31T18:31:33.000Z

yeah sorry there was a big delay before your answer, so I switched to another tool and changed the environment, forgot how it was.