Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding new dataset import to existing project error 409 File with same name already exist #5563

Closed
2 tasks
randubin opened this issue Jan 10, 2023 · 0 comments · Fixed by #5909
Closed
2 tasks
Assignees
Labels
bug Something isn't working server

Comments

@randubin
Copy link

My actions before raising this issue

Expected Behaviour

Project imported

Current Behaviour

Error 409
Error: tus: unexpected response while creating upload, originated from request (method: POST, url: http://localhost:8080/api/projects/1/dataset/, response code: 409, response text: "File with same name already exists", request id: n/a).

e @ cvat-app.tsx:357
  showErrors @
  componentDidUpdate @
  ss @
  vl @
  t.unstable_runWithPriority @
  Ua @
  gl @
  rl @
  (anonymous) @
  t.unstable_runWithPriority @
  Ua @
  qa @
  Ga @
  al @
  notify @
  notifyNestedSubs @
  a @
  v @
  (anonymous) @
  (anonymous) @
  dispatch @
  (anonymous) @
  await in (anonymous) (async)  
  (anonymous) @
  N @
  (anonymous) @
  onFinish @
  (anonymous) @
  Promise.then (async)  
  Re.submit @
  onOk @
  w @
  Q @
  s @
  f @
  (anonymous) @
  v @
  ot @
  rt @
  it @
  pt @
  j @
  H @
  Xt @
  $t @
  t.unstable_runWithPriority @
  Ua @
  I @
  qt @



Note if I upload to a different project it is uploading with success. ### Possible Solution

Steps to Reproduce (for bugs)

  1. When i upload the same import task to one project it fails.
    1.When I upload the same task to another project it upload fine.
  2. All import tasks fail for that project

Context

Can't upload new imported tasks to a project.

Your Environment

  • Git hash commit (git log -1): commit 760f40d (HEAD -> develop, origin/develop, origin/HEAD)
  • Docker version docker version (e.g. Docker 17.0.05): v4.11.1.
  • Are you using Docker Swarm or Kubernetes?no
  • Operating System and version (e.g. Linux, Windows, MacOS): windows
  • Code example or link to GitHub repo or gist to reproduce problem:
  • Other diagnostic information / logs:
    Logs from `cvat` container
@zhiltsov-max zhiltsov-max added bug Something isn't working server labels Mar 24, 2023
@Marishka17 Marishka17 mentioned this issue Mar 24, 2023
9 tasks
SpecLad added a commit that referenced this issue Jun 2, 2023
Fixed:
- wrong location of tmp file when importing job annotations
- ```Traceback (most recent call last):
File
"/home/maya/Documents/cvat/.env/lib/python3.8/site-packages/rq/worker.py",
line 795, in work
      self.execute_job(job, queue)
File "/home/maya/Documents/cvat/cvat/rqworker.py", line 37, in
execute_job
      return self.perform_job(*args, **kwargs)
File
"/home/maya/Documents/cvat/.env/lib/python3.8/site-packages/rq/worker.py",
line 1389, in perform_job
      self.handle_exception(job, *exc_info)
File
"/home/maya/Documents/cvat/.env/lib/python3.8/site-packages/rq/worker.py",
line 1438, in handle_exception
      fallthrough = handler(job, *exc_info)
File "/home/maya/Documents/cvat/cvat/apps/engine/views.py", line 2233,
in rq_exception_handler
      rq_job.exc_info = "".join(
  AttributeError: can't set attribute
  ```

Resolves #5773
Resolves #5563

- root causes of the issues: 
  - the annotation file was uploaded to the server by tus protocol and
rq job was created but no one next requests for checking status were not
made. (e.g. user closed the browser tab)
  - the annotation file was uploaded to the server by tus protocol but
rq job has not yet been created (e.g cvat instance restarted)
  - tasks/projects creation from backups with the same name at the
same time by different users

Co-authored-by: Roman Donchenko <roman@cvat.ai>
Co-authored-by: Maxim Zhiltsov <zhiltsov.max35@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working server
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants