nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Child Item

Update your Dropbox Python Core SDK

Itay D.

Hi!

We have recently received a message indicating that the old version of the Python SDK we're using (1.6) is going to be deprecated on Aug 1, 2016.

Had a couple of quick questions about this:

If we were to continue using the 1.6 SDK, what sort of issues should we expect? Will all API calls fail due to the expired certificate?
Is there a way to work around this and continue using 1.6? Maybe a way to use the newer certificate with the old SDK?

The reason we’re asking this is that in the past, we’ve had some issues upgrading to newer Dropbox SDKs, and we’re on a tight schedule with other projects until Aug 1st.

Thanks!

Itay

Find more posts tagged with

API

Abuse

Comments

Greg-DB

1. Yes, your API calls will fail once the Dropbox certificates are changed to ones not covered by the certificate file included in your copy of the SDK

2. We recommend upgrading the SDK entirely, and we'll be happy to help with any issues you have while doing so. Looking at the CHANGELOG.md file, I don't see any breaking changes between 1.6 and 2.x, so it should just be a matter of dropping in the new library.

That said, one alternative to upgrading the SDK entirely is to instead just replace the dropbox/trusted-certs.crt file in your copy with the one from the new versions of the SDK.

Itay D.

Thank you for the quick response, Gregory!

We understand that upgrading the entire SDK is the best option.

If for some reason we are unable to complete the upgrade and choose to replace the certificate, what is the safest way to test (before Aug 1) that it works?

Thanks!

Greg-DB

There isn't a great way to test this from your side ahead of time, since the actual change will just be a change in the certificate being used on the Dropbox API servers. As long as the upgrade (either SDK or just certificate file) works when you do the upgrade, we don't expect any issues when the new certificate is in use. That said, we'll of course be available and monitoring for issues when we make the change.

Itay D.

Hi Gregory,

After upgrading the Dropbox SDK, we ran into the following warning:

"Connection pool is full, discarding connection: api.dropbox.com"

It seems as though the number of concurrent connections exceeds the allocated number of connections allowed in the pool.

What is the best approach of handling this?

Thanks!

Greg-DB

The connection pooling should be handled for you. Are you getting failed requests when you see this warning logged?

If you'd like, you can control the max_connections by creating a session:

https://dropbox-sdk-python.readthedocs.io/en/master/moduledoc.html#dropbox.dropbox.create_session

and then passing that in when creating a client:

https://dropbox-sdk-python.readthedocs.io/en/master/moduledoc.html#dropbox.dropbox.Dropbox

Itay D.

I believe these connections are being dropped, so some of the work is not executed when it should be.

Any idea why the connection pooling is not working correctly?

If we use the session to increase the number of connections in the pool, it's very likely that we'll still see this warning, only less frequently (now the number of connections is 8, I believe).

Thanks!

Greg-DB

Can you elaborate on what you mean when you say you "believe these connections are being dropped, so some of the work is not executed when it should be"? Is there any error or output you can share?

Itay D.

These "connection dropped" logs are printed as part of /delta calls being made to the Dropbox API. What I mean is that I believe some of these requests never make it to the host api.dropbox.com since they are dropped by the urllib3 library.

Is there anything else we could try except creating a session to increase the max number of connections per pool?

Thanks!

Greg-DB

Specifically, I mean are you getting anything else from your app (e.g., other output or errors) that leads you to believe that's the case beyond that warning log message though? I believe that warning just indicates that a freed connection wasn't being returned to the pool because the pool is already full, not that any requests are being dropped. It doesn't indicate an issue that necessarily needs to be fixed, but you can increase the max_connections if you want to.