[Bug]: LogCommits Since Parameter Format Mismatch in Python Client #6970
Labels
bug
Something isn't working
contributor
no stale
Using this label will prevent items from being marked as stale
What happened?
We are experiencing errors while trying to use the new
since
argument forlog_commits
using the Pythonlakefs_sdk
client.It appears there is a format mismatch between the Python client and the LakeFS API. Looking closer, the Python client uses the format string
"%Y-%m-%dT%H:%M:%S.%f%z"
which outputs values like"2023-05-09T09:53:33.853466"
. However, the API expects values like"2006-01-02T15:04:05Z07:00"
. As a result, the API returns an HTTP 400 Bad Request.To reproduce:
I tried passing my own string value (e.g.
since="2023-11-09T10:00:00"
), but it looks like the client converts the string into a datetime first anyway before then formatting it using its own format string.As a workaround, I was able to successfully change the client's datetime format string. However, I'm not sure that this is the expected solution.
Expected behavior
Expected behavior is that the Python client should be compatible with the API without me needing to configure the format string.
lakeFS version
LakeFS Cloud
How lakeFS is installed
Cloud
Affected clients
lakefs-sdk==1.1.0.2
Relevant log output
Contact details
No response
The text was updated successfully, but these errors were encountered: