Closed dotsdl closed 10 months ago
No there was a bug in some of the JWT handling. Also reported in #784, fixed in PR #783.
I just increased the expiration time, which should keep that at bay for a bit until the next release (should be soon).
Fixed and released in v0.52
Describe the bug
After leaving a
PortalClient
instance idle for approx. 24hrs, usinglist_datasets()
yields:Creating a new client instance resolved the issue, but this is still unexpected behavior.
Is this a symptom of using two tokens (an "access" token and a "refresh" token) with separate expirations for auth? Or is it something else?