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
It appears that when using the client.update_dataset_metadata(request) method to update the dataset metadata, it will return the following error if the dataset already has metadata: invariant_sdk.types.exceptions.InvariantError: Error calling method: PUT for path: /api/v1/dataset/metadata/your_dataset_name
Reproduction of the issue:
After successfully pushing traces to explorer using client.push_trace(request) and client.update_dataset_metadata(request), repeating the second command will trigger the above error.
Suggestion:
It would be helpful to have a specific error message just like those for error code 500, 401, 404:
f"Server error caused failure when calling method: {method} for path: {pathname}."
) frome
ifresponse.status_code==401:
raiseInvariantAuthError(
f"Authentication failed when calling method: {method} for path: {pathname}."
) frome
ifresponse.status_code==404:
This one returns 403.
Add a feature to overwrite the old metadata for update (such as a force=true parameter) or add a feature to delete the old metadata (supporting a DELETE request only targeting metadata) without needing to delete the whole dataset.
The text was updated successfully, but these errors were encountered:
Description:
It appears that when using the
client.update_dataset_metadata(request)
method to update the dataset metadata, it will return the following error if the dataset already has metadata:invariant_sdk.types.exceptions.InvariantError: Error calling method: PUT for path: /api/v1/dataset/metadata/your_dataset_name
Reproduction of the issue:
After successfully pushing traces to explorer using
client.push_trace(request)
andclient.update_dataset_metadata(request)
, repeating the second command will trigger the above error.Suggestion:
invariant-sdk/python/invariant_sdk/client.py
Lines 149 to 157 in 50c0ade
force=true
parameter) or add a feature to delete the old metadata (supporting aDELETE
request only targeting metadata) without needing to delete the whole dataset.The text was updated successfully, but these errors were encountered: