-
Notifications
You must be signed in to change notification settings - Fork 2
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
Not completing discovery #130
Comments
Hello, Thank you |
From the logs, you have a single project with a tone of files, right? Sorry for all the questions but I need to understand the problem, from the logs, it discovers the content, looks like the assets are created, they are sent to the processing queue, but there are no errors.... |
When browsing the SQL Lite database, there are only 314 records in the project_assets table and 1 record in the projects table. This matches what is shown in the UI, but does not match what is in the library folder. |
Any ideas? |
Hi, I've looked a bit at it, I seems there is a deadlock behaviour during the discovery process. I need to confirm my theory and make a fix... |
Thanks. I would be happy to test it when you are ready |
I've found the issue. |
@johnwhobbs Could you please test this package https://github.com/Maker-Management-Platform/agent/pkgs/container/agent/220710051?tag=130-not-completing-discovery ? |
Works great now. All models present and thumbnails created for each. Thanks!!!! |
I'm gonna push this as an hotfix |
I have multiple projects with hundreds of .stl files. All of the files are scanned and added to the library; however the process that creates the PNG files for each one just stops at some point and will never restart, even if I start a new discovery scan or reboot the container. And to accomplish this, I had to add .stl files to the library folder a little at a time. If they were all in there at first start of the Agent container, discovery would get to some point and just stop. Files aren't added to the library and PNG files are not created.
The text was updated successfully, but these errors were encountered: