Open siddtmb opened 7 months ago
tried changing ports as well....
Hello, I do not think that somebody inside the team really uses these debug configurations from VSCode, because debugging from Google Chrome IMHO is more convenient. So, I would recommend to avoid them for now.
We definitely need to update the guides.
Regardless. It does not actually work. I cannot get development environment on localhost:3000 even after following all the steps.
Be sure you up front-end dev server.
You do that by doing the F5 and server:debug, right? That is exactly what is failing, and i needed help in that.
Running server:debug causes an error in VSCode popup: Debug Stopped
I'm facing a similar issue. Did it get resolved for you? If yes, could you describe what you did?
I gave up... @Mansin-nd moved on to some other things cuz it clearly wasn't launching. Might launch now will retry but I have no immediate need for it and it seems like a hassle. I needed to make a better tracking thing where it would track for N number of frames at once instead of the sluggish tracking it was doing before.
any solution? I also face same problem when I trying to connect 127.0.0.1:3000 in browser(chrome) it response "cannot connect to server"
Actions before raising this issue
Steps to Reproduce
Followed all the instructions on https://opencv.github.io/cvat/docs/contributing/development-environment/ with a fresh repository and a fresh python3.10 environment. nodejs version 16.20.2
Everything works fine till I press F5 to
server:debug
orserver:chrome
Running
server:debug
causes an error in VSCode popup:Debug Stopped
Runningserver:chrome
causes errors in VSCode Debug Console:Regardless, the server at localhost:7000 is unavaiable and localhost:3000 gives gateway error
It is frustrating how every time there is some new error with the dev environment which is not documented. Previously it was python3.10
Environment