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

After update to v1.2.0 tasks created prior to update cannot be used with projects #2972

Closed
2 tasks done
georkap opened this issue Mar 18, 2021 · 2 comments · Fixed by #3164
Closed
2 tasks done

After update to v1.2.0 tasks created prior to update cannot be used with projects #2972

georkap opened this issue Mar 18, 2021 · 2 comments · Fixed by #3164
Assignees
Labels
bug Something isn't working

Comments

@georkap
Copy link

georkap commented Mar 18, 2021

My actions before raising this issue

At the 1.2.0 version of cvat it is not possible through the UI to assign an existing task (created prior to v.1.2.0) to a new project.

Via the administration panel it is possible to assign the existing tasks to projects, however the tasks are deemed unusable. These tasks cannot open anymore either via Projects>Task>Job or via Tasks>Job and the following error is shown from the Browser Console.

Uncaught (in promise) TypeError: Cannot read property 'activeChunkRequest' of undefined
    at Object.h [as resolveCallback] (frames.js:133)
    at Worker.e.onmessage (cvat-data.js:316)
Failed to load resource: the server responded with a status of 500 (Internal Server Error)    :8080/api/v1/jobs/39/annotations:1 
Error: Request failed with status code 500. "\n<!doctype html>\n<html lang=\"en\">\n<head>\n  <title>Server Error (500)</title>\n</head>\n<body>\n  <h1>Server Error (500)</h1><p></p>\n</body>\n</html>\n".
e @ cvat-app.tsx:208

If the task is reverted to not being assigned to any project then it is usable again though Tasks.

Is this behavior intended (not using old tasks with projects)? Is there a way to make old tasks/jobs usable via projects in v1.2.0?

@nmanovic nmanovic added the bug Something isn't working label Mar 18, 2021
@nmanovic nmanovic added this to the Backlog milestone Mar 18, 2021
@nmanovic
Copy link
Contributor

@georkap , thanks for the report.

@georkap
Copy link
Author

georkap commented Apr 1, 2021

Update: The same behavior is experienced for tasks created after the update to 1.2.0, i.e., if the project is changed from the admin panel the task is not accessible unless it is reverted to its original project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants