Jo Booth

/jira create > [Workflow run](https://github.com/HumanSignal/label-studio/actions/runs/10708463885) > Jira issue [TRIAG-823](https://humansignal.atlassian.net/browse/TRIAG-823) is created [TRIAG-823]: https://humansignal.atlassian.net/browse/TRIAG-823?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ

Hi @cgrtrifork, thanks for raising this issue and sending a PR! I'll flag this for the team.

Hi @hemangjoshi37a - I'm not very familiar with Roboflow, but are you able to export your roboflow data as JSON or similar, then run some kind of batch job on...

Hi @lanluu, this will be addressed on develop soon: https://github.com/HumanSignal/label-studio-sdk/pull/271/files#diff-50c86b7ed8ac2cf95bd48334961bf0530cdc77b5a56f852c5c61b89d735fd711 Unfortunately this upgrade most likely won't make it into our upcoming 1.13.1 release, but it'll be in the next one.

Hi @mkrupczak3, Migrations should be automatic but it looks like you've got one that failed to run. Let's get that fixed. Try these steps: ``` $ docker compose up -d...

Ah, I should have mentioned that it'll be necessary to switch your label studio version to the later one that you're trying to run before running the above steps :sweat_smile:....

I'm not really sure what effect upgrading with pip inside the container would have. Can you instead try Label Studio 1.11.0 and rebuild your containers? I think I understand what...

> Tried label studio 1.11.0 but still no luck: > > ``` > I have no name!@31d472712473:~/label_studio$ python3 manage.py migrate > => Database and media directory: /label-studio/data > => Static...

This makes sense; the column discussed was added and then removed, so a version of LS that predates the column will also work. Your logs from Docker show the backend...

Could you try this in the container while running 1.11, much like we did before? ``` $ docker compose up -d $ docker exec -it label-studio-app-1 bash $ cd label_studio...