-
-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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
Fix flaky integration tests on CI #7866
Comments
This change is mostly motivated to get a more stable CI build (we're building the Hugo site there, with Instagram and Twitter shortcodes sometimes failing). Fixes gohugoio#7866
This change is mostly motivated to get a more stable CI build (we're building the Hugo site there, with Instagram and Twitter shortcodes sometimes failing). Fixes gohugoio#7866
This change is mostly motivated to get a more stable CI build (we're building the Hugo site there, with Instagram and Twitter shortcodes sometimes failing). Fixes gohugoio#7866
This change is mostly motivated to get a more stable CI build (we're building the Hugo site there, with Instagram and Twitter shortcodes sometimes failing). Fixes gohugoio#7866
This change is mostly motivated to get a more stable CI build (we're building the Hugo site there, with Instagram and Twitter shortcodes sometimes failing). Fixes gohugoio#7866
I'm assuming this is a rate limit issue? I wonder if it would it help to add backoff+retry options to the getJSON func. |
We're not adding stuff to |
This change is mostly motivated to get a more stable CI build (we're building the Hugo site there, with Instagram and Twitter shortcodes sometimes failing). Fixes gohugoio#7866
This change is mostly motivated to get a more stable CI build (we're building the Hugo site there, with Instagram and Twitter shortcodes sometimes failing). Fixes gohugoio#7866
This change is mostly motivated to get a more stable CI build (we're building the Hugo site there, with Instagram and Twitter shortcodes sometimes failing). Fixes gohugoio#7866
This change is mostly motivated to get a more stable CI build (we're building the Hugo site there, with Instagram and Twitter shortcodes sometimes failing). Fixes gohugoio#7866
This change is mostly motivated to get a more stable CI build (we're building the Hugo site there, with Instagram and Twitter shortcodes sometimes failing). Fixes #7866
Finally!! cc: @kaushalmodi |
@onedrawingperday Thanks for tagging me here (and even remembering that I very much was troubled by that getJSON error). |
@kaushalmodi You're welcome. I've also been beaten by this error myself and I followed the discussion back then between you and Bjørn Erik closely. So of course, I remembered. |
Otherwise it causes build failures. See gohugoio/hugo#7866
Due to failed HTTP requests the instagram short code has been removed from https://github.com/gohugoio/hugoBasicExample. However, approximately 20 whitelisted themes on www.themes.gohugo.io use a (customized) version of the https://github.com/gohugoio/hugoBasicExample that still include the instagram shortcode. Thus the demos for this themes can't be build. As mentioned by Alexandros here the error can be suppressed for the whitelisted themes with an config option once Hugo 0.77.0 is released. The actual reason why When using the |
Hello @digitalcraftsman
The above merits its own issue in the main issues tracker. Apparently Instagram is ending the last remaining public API endpoint. The Instagram shortcodes will either need to be refactored or removed. |
Hello Alexandros, I've added the information for context but created a new issue as suggested by you. |
Closes #82 and #84 Please see the following link for more information sourrounding the issues with the Instagram Shortcode. gohugoio/hugo#7866
Closes lxndrblz#82 and lxndrblz#84 Please see the following link for more information sourrounding the issues with the Instagram Shortcode. gohugoio/hugo#7866
Otherwise it causes build failures. See gohugoio/hugo#7866
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Also similar for the Twitter.
The text was updated successfully, but these errors were encountered: