Skip to content
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

LoadError: cannot load such file -- algolia/insights #108

Closed
mkiser opened this issue Dec 19, 2018 · 5 comments
Closed

LoadError: cannot load such file -- algolia/insights #108

mkiser opened this issue Dec 19, 2018 · 5 comments

Comments

@mkiser
Copy link

mkiser commented Dec 19, 2018

Seems like something changed with algoliasearch because Jekyll build now fails on Jekyll-Algolia as of a few hours ago

Error => https://travis-ci.org/mkiser/WTFJHT/builds/470107663#L645

Here's my repo: https://github.com/mkiser/WTFJHT

I cleared the Travis-CI cache, too, but it still errors. Commenting out Jekyll-Algolia resolves the issue.

$ ruby --version
ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-linux]
$ rvm --version
rvm 1.29.3 (latest) by Michal Papis, Piotr Kuczynski, Wayne E. Seguin [https://rvm.io]
$ bundle --version
Bundler version 1.17.2
$ gem --version
3.0.0
@pixelastic
Copy link
Collaborator

Thanks. Seems like we failed to update correctly the dependencies of algoliasearch. You can add gem 'algoliasearch', '1.24' to your Gemfile temporarily to force using the latest working version.

@julienbourdeau
Copy link

@mkiser Thank you for reporting this issue.

I released 1.25.0 earlier today but didn't register everything correctly in the gemspec. @pixelastic helped me fixing it and 1.25.1 is out, everything should be fin now.

Thanks again 👍

@mkiser
Copy link
Author

mkiser commented Dec 19, 2018

Not sure 1.25.1 fixed this? I cleared the build cache and restarted the build and got the same thing:

https://travis-ci.org/mkiser/WTFJHT/jobs/470195818#L645

@pixelastic
Copy link
Collaborator

Thanks @mkiser, we're on it. Seems like we have a few hiccups with the release of the ruby client. We're working on it, to make sure all needed files are correctly sent to rubygems.

In the meantime, I released v1.4.10 of jekyll-algolia that pins the dependency to 1.24 (last working version), so the error should now disappear from your CI quickly.

@pixelastic
Copy link
Collaborator

And... issue is fixed in algoliasearch 1.25.2, so I released jekyll-algolia 1.4.11 that uses it :)

Everything should be all green now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants