-
Notifications
You must be signed in to change notification settings - Fork 1
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
Issues uploading images from NBU #23
Comments
@NickLaiacona and @camdendotlol - It looks like the issue with manifests not being generated was still being caused by an R15 error on Heroku. Although we offloaded the image conversion to a worker, ImageMagick itself was still trying to consume more memory than allowed by the Hobby dyno. To avoid this issue, I've made the following changes on the IIIF Cloud staging environment:
I tested by uploading all of the folders in this Google drive as batches (results currently on staging) and confirmed that the IIIF viewer displayed the same number of images that were uploaded. I would, however, encourage additional testing, as there may be use cases I am not aware of. One important thing to note: Should any issues arise in the future, I've added Papertrail to the app to increase visibility into the logging. The Rails/ActiveJob logs are already quite verbose, so I didn't see the need to manually add any additional logging. Papertrail should also allow searching by time, keyword, etc. |
I think I can address that on NBU's end with the |
It appears as though some resources uploaded to IIIF Cloud are not having manifests generated.
The text was updated successfully, but these errors were encountered: