HumanSignal / HumanSignal/label-studio-sdk

api/storages/azure using credentials fail with validation error

Open
#433 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
192
Forks
127
Avg merge
1d 18h
Merged PRs (30d)
1

Description

Dear Label Studio Team,
something strange has happened lately and I cannot figure out why:
Previously, when creating cloud storages (azure), UI or python SDK (project.connect_azure_import_storage), we had to state the account name and account key.
Now, these values seem to be pre-filled (UI: many dots, SDK: no values needed)
But the pre-filled values work for both SDK and UI
Unfortunately, this seems to have broken our code using the SDK as we are specifying the account name and account key in the SDK call
We are using the correct values, but we always get a validation error:
ERROR:label_studio_sdk._legacy.client:

--------------------------------------------
Request URL: https://labelstudio-wallscanner-webapp-dev.azurewebsites.net/api/storages/azure
Response status code: 400
Response content:
{
“id”: “6cd686f2-46fa-467c-983e-0b9be8eea7fd”,
“status_code”: 400,
“version”: “1.13.1”,
“detail”: “Validation error”,
“exc_info”: null,
“validation_errors”: {
“non_field_errors”: [
“Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.
To avoid this, we can simply omit the account name and key (or use None), but that is just too weird of a solution!
All our other SDK calls work perfectly…
Any idea what is wrong and how to fix it?
Thanks!
PS: locally, I am using label_studio_sdk-1.0.8, on our data-processing pipeline, we are using label_studio_sdk-1.0.10

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.