-
Notifications
You must be signed in to change notification settings - Fork 321
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
Expose way to keep track of a file's upload or download progress #37
Comments
This is possibly common enough to add special support. But for now, there are some workarounds.
The assumption (that all the data read before the call to |
In the v1 API, the |
v2 has upload_session_start / upload_session_append / upload_session_finish, but its not exactly for this use-case I don't think. Besides there's still no progress update mechanism for download, so would certainly be useful to get that in there, shouldn't be hard at all. |
👍 Yeah it should be straight forward enough. Awesome job on opening the client SDK on github - I have a fork of v1 with a single lonely patch which nowadays will be a pull request 😄 |
@cakoose thanks for the workaround, I'll take a look at doing that for now. |
@cakoose your workaround is better than nothing, thanks! |
@cakoose I am confused in using the return type of files_download_to_file. as per the documentation The return types are metadata and request object. They are returned only after the file gets downloaded. Moreover in this case, tuple is returned. But when printing it, I find only the metadata.
Thanks in advance. |
Use |
@Lakshman-LD function files_download_to_file have mistake in their doc description. |
@aicpp thank you for pointing this out, was driving me crazy |
Has a way to track download progress with |
@ianshmean No, unfortunately not. |
Having an optional delegate method argument in the files_upload / files_download methods so that we can update progress UI and whatnot when uploading and downloading files would be really useful.
The text was updated successfully, but these errors were encountered: