question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Not able to open the add cloud storage dialog

See original GitHub issue

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:

  1. Go to ‘Project > Setting > Cloud Storage’
  2. Click on ‘Add Source Storage’
  3. 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

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:15 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
suvojit-0x55aacommented, Jun 16, 2021

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

1reaction
SMarwencommented, Jun 15, 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

Read more comments on GitHub >

github_iconTop Results From Across the Web

Troubleshooting | Cloud Storage
Solution: Check that your client, or any intermediate proxy, is not adding an Authorization header to requests to Cloud Storage.
Read more >
Office 365 for Mac: Open dialog shows only cloud storage
When I want to open a file from within an office application, I tip cmd-O to get the project catalog. Normally this would...
Read more >
5 Ways to Fix OneDrive When You Cannot Open Your Files
1. Check OneDrive's File Permissions · 2. Reset OneDrive · 3. Check if the File Is "On-Demand" · 4. Check Storage Sense Settings...
Read more >
ArcGIS Pro Create Cloud Storage Error — Blog - open.gis.lab
Go Insert tab >> Connections >> Add Cloud Storage Connection. In Catalog pane >> Right click on empty space >> Add Cloud Storage...
Read more >
Troubleshooting Transfers - IBM
The article contains tips and procedures to troubleshoot failed or incomplete Aspera on Cloud transfers.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found