We’re Still Here to Help (Even Over the Holidays!) - find out more here.
Forum Discussion
Silent failures with files_upload and Python API
I am having trouble figuring out the right way to address this issue I am having with one of my apps. I loop over some files and create some worker threads (just a few threads) to upload files to ...
Greg-DB
Dropbox Community Moderator
Dropbox Community ModeratorYes, it sounds like you have the right handle on this now. For the Dropbox API calls themselves, they should either return a result, or raise some sort of exception (such as an API error, or some network error, etc.). They shouldn't fail silently.
It seems that the issue with them failing silently was due to the thread pool throwing away the threads that take a certain amount of time, so yes, you'd want to configure the thread pool accordingly for this use case. Exactly how you do so is up to you, but you could potentially set the thread expiration to be sufficiently large to accommodate however long the API call might take (before succeeding or failing in some way; and you can set a timeout on the Dropbox client as you mentioned), or perhaps disable the thread expiration entirely, if possible.
I am hesitant to pass None or disable timeouts entirely. I would rather restart the thread once I know a timeout has occurred. There is a whole slew of internet connectivity issues that could happen on the user end which I don't want to mask by just waiting infinitely.
Thanks for your reply!
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
