-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Upgrading from 2.22.0 to 2.23.1 fails with broken assets. #8803
Comments
Could you please clarify what you mean? |
Sorry, that wasn't clear.
The video is simply gone from the UI. |
|
Hi, The "problem" was introduced by this Pull Request: Prepare chunks in a worker process. Since they use a dedicated container for chunk generation now this container also needs to have access to the shared volume: Example Updating my
PS: The documentation currently does not mention the |
I am not using anything extra, this is just a default setup.
|
You are right, we definitely need to update the documentation. |
@ggozad Ok, looks like a slightly different problem. Should I therefore file a separate issue for my problem or will it suitable to handle both problems in this issue? |
Hi @ggozad, I’m encountering the same issue you described, and it seems to be related to tasks imported through the share path feature. I suspect it might be caused by the changes introduced in the Pull Request that prepared chunks in a worker process. As you mentioned, since the chunk generation now occurs in a dedicated container, it’s crucial that this container has access to the shared volume. I made similar updates to my docker-compose.override.yml to ensure the images are visible in the annotation view again. However, I’m still facing issues with the preview images being replaced by placeholders. Here’s the relevant error log from my setup (version 2.23.0): Verify Open In Editor
Additionally, I noticed that the documentation does not currently mention the cvat_worker_chunks container in the share path section. I discovered this required configuration change by reviewing the pull request itself. I also observed a similar traceback when trying to access job data: Verify Open In Editor
It seems like there might be a deeper issue with how the chunk data is being handled in the new setup. If anyone has insights or suggestions on how to resolve this, I would greatly appreciate it. Thank you for your help! Best, |
@ggozad please provide logs from cvat_worker_chunks container as well |
Here you go:
|
@ggozad try to clear the cache with |
@azhavoro this seems to resolve the issue! Thank you! |
I don't think so, it should be handled correctly in the code. Unfortunately, I missed this point in the PR. In any case, it can be fixed either by clearing the cache, or it would work without any action in no more than 24 hours, after the cache item would have expired |
I did verify on another mirror I had set up for testing that indeed after 24h the cache keys are expired and everything works fine. |
fwiw, we are experiencing the same issue--clearing the cache as described did not work; I will spin up a mirror and see if it self resoles within 24 hours |
Actions before raising this issue
Steps to Reproduce
Images and video data are missing. Reverting to 2.22.0 and restoring from backup works fine.
Expected Behavior
I would expect to be able upgrade without loosing all the images/videos.
Possible Solution
No response
Context
No response
Environment
The text was updated successfully, but these errors were encountered: