You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Traces logged to the same project with versions 1.3.0 and 1.3.1 of the Python SDK appear out of order.
Issue:
This is due to the fact that the SDK was using the Python package uuid7 to generate the unique ids that are used to sort traces in the UI. However this package has an issue with the way the ID is generated which caused issues when logging traces from both the Python SDK and the upcoming Typescript SDK.
Resolution
To resolve this issue, we moved to a new library called uuid6 that doesn't have the same issue as the previous library. This change was released in version 1.3.1 of the Python SDK.
If you have already logged traces with version <=1.3.0, we recommend logging traces to a new project so that new traces appear at the top of the page.
The text was updated successfully, but these errors were encountered:
jverre
changed the title
[Bug]: Breaking change - Some traces appear at the end of projects
[Bug]: Some traces appear at the end of projects
Dec 27, 2024
What component(s) are affected?
Opik version
Describe the problem
Traces logged to the same project with versions
1.3.0
and1.3.1
of the Python SDK appear out of order.Issue:
This is due to the fact that the SDK was using the Python package
uuid7
to generate the unique ids that are used to sort traces in the UI. However this package has an issue with the way the ID is generated which caused issues when logging traces from both the Python SDK and the upcoming Typescript SDK.Resolution
To resolve this issue, we moved to a new library called
uuid6
that doesn't have the same issue as the previous library. This change was released in version1.3.1
of the Python SDK.If you have already logged traces with version
<=1.3.0
, we recommend logging traces to a new project so that new traces appear at the top of the page.The text was updated successfully, but these errors were encountered: