-
Notifications
You must be signed in to change notification settings - Fork 9
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
gatsby-source-flamelink plugin is intermittently failing to download images from flamelink(warning Failed to download image: ) #50
Comments
You could try the following before doing a build As for the images, if the image download fails, it is most likely related to a Firebase failure. It would be really helpful if you could provide some more information as to what you think might be causing the issue, or if possible, create a pull request for a fix. |
Hi @dewetvdm , As I mentioned previously, it is an intermittent issue. I think it is a timeout issue. we may need to modify the code to increase the timeout bit more. |
I am having this problem as well. We are also using the Blaze plan from Firebase. Any updates on this issue? EDIT: I think this could be caused by the firebase-admin dependency not being updated. gatsby-source-flamelink has 11 high severity vulnerabilities due to firebase-admin and google-p12-pem |
Hello, I have since learned that what is causing the issue is likely that you are using an old version of gatsby-source-filesystem. Please bump this as well :) |
This plugin was working perfectly earlier, nowadays it is started having the problem of unable to download the image from flamelink. If the images are not downloaded obviously gatsby site build will not happen. Moreover, this plugin is working sometimes and not working sometimes. It shows the below warning for many image files. Though it saying it is a warning, but it is actually an error as if the images are not downloaded gatsby build will not succeed.
warning Failed to download image: 7C0au0Flo8y8q4fwGjvr
The text was updated successfully, but these errors were encountered: