label-studio: Not able to open the add cloud storage dialog

Describe the bug When I click on the “Add Source Storage” and “Add Target Storage” the dialog box appears for few moment and closes.

To Reproduce Steps to reproduce the behavior:

Go to ‘Project > Setting > Cloud Storage’
Click on ‘Add Source Storage’
Dialog box doesn’t open

Expected behavior Expect dialog box to open to add cloud storage

Screenshots

Uncaught (in promise) TypeError: v.map 
is not a function
    at StorageForm.js:51
    at ia (react-dom.production.min.js:157)
    at Ra (react-dom.production.min.js:176)
    at $l (react-dom.production.min.js:271)
    at Ts (react-dom.production.min.js:250)
    at js (react-dom.production.min.js:250)
    at Ss (react-dom.production.min.js:250)
    at gs (react-dom.production.min.js:243)
    at react-dom.production.min.js:123
    at t.unstable_runWithPriority (scheduler.production.min.js:18)

Environment (please complete the following information):

OS: Ubuntu 18.04
Label Studio Version: 1.0.2

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 15 (4 by maintainers)

Most upvoted comments

Deleted older repo, exported data with a fresh build, it worked.

suvojit-0x55aa on Jun 16, 2021

Hi @suvojit-0x55aa The root cause of the problem is that storages are not shown because of missing return storage_list in label_studio/io_storages/all_api.py, this bug was solved in recent versions.

In order to solve it, you should rebuild the image or download the latest docker image and make sure that labela_studio_app is using the latest image.

If you have built the container using the old version, then label_studio folder is stil linked to static volume, so changes in this folder will not be applied in the container, thus the bug will not be solved

To check this out you can do :

docker-compose up
docker exec -it label-studio_app_1 bash
ll

Finally the steps become :

docker-compose down
docker volume prune
docker build -t . heatexlabs/label-studio:latest .
docker-compose up

Of course docker volume prune is here to delete old volumes and hence old code

SMarwen on Jun 15, 2021

yes exactly, in this line here : https://github.com/heartexlabs/label-studio/blob/0c237b9318599339823e5f19ac30020796f20997/docker-compose.yml#L36 Label studio is linking the code to this volume So if you used docker compose with previous version, you need to delete the volume and spin up the services again I asked why they did it this way on slack, but I got no answer @makseq so in short, steps are :

docker-compose down
docker volume prune
docker-compose up

SMarwen on Jun 12, 2021