cvat-ai / cvat

Annotate better with CVAT, the industry-leading data engine for machine learning. Used and trusted by teams at any scale, for data of any scale.
https://cvat.ai
MIT License
12.64k stars 3.01k forks source link

Error during fetching a job #5797

Open Answergeng opened 1 year ago

Answergeng commented 1 year ago

My actions before raising this issue

QQ截图20230302174858 Browser Console details: Error: Request failed with status code 504. "<!DOCTYPE HTML PUBLIC \"-//IETF//DTD HTML 2.0//EN\">\n<html><head>\n<title>504 Gateway Timeout</title>\n</head><body>\n<h1>Gateway Timeout</h1>\n<p>The gateway did not receive a timely response\nfrom the upstream server or application.</p>\n</body></html>\n".

Steps to Reproduce (for bugs)

  1. Create a new task by Connected file share(coco val 2014)
  2. Upload annotations - instances_val2014.json
  3. Try to open the job and the error raises
  4. Before the upload can open the job without any problems

Expected Behaviour

Current Behaviour

Possible Solution

Context

Your Environment

saifkhichi96 commented 1 year ago

I have the same error with some of my jobs which contain large videos (150-200 MB). The jobs can open fine without annotations, and I was previously able to annotate them too. But now, they give a timeout error when opening them. I can export the dataset of the job, which consists of a lot of masks and the export size is about 450 MB for a single video.

The same videos can open fine if I create new jobs with them, but if I upload the exported annotations to these newly created jobs, I start getting the same error again.

nmanovic commented 1 year ago

@saifkhichi96 , @Answergeng , we will look at the issue. Thank you for the report.

@SpecLad , it can be a part of REST API redesign.

subham9777 commented 1 year ago

Hi, facing the same issue above on a self-hosted aws ami, large 6k images with annotation job is not opening on the UI. Worked well till yesterday night

yuerout commented 2 weeks ago

Hi! I was wondering if anything has been done about this -- facing the same issue now