-
Notifications
You must be signed in to change notification settings - Fork 27
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
Indexing fails on newly fetched gems #38
Comments
Hi and thanks for your feedback. |
Same version as in the other issue (#39) that I created:
|
Hum, really strange, this part of code really bothers me. Look like there is a bug when updating indexes, but there is also a bug when trying to fetch a gem with many dependencies (consuming all memory)... |
Hello, I think we are hitting the same issue now. Installing a gem works, but installing a different gem fails afterwards:
|
Hello, I applied the changes from commit 719f97a in our instance, but the problem is still appearing. Gemirro server
gem install
|
I'm experiencing the same issue as well Server-side:
Client-side
The first gem fetched and installed successfully and second and next is failing with error until gemirror webserver will be restarted:
On the server side I have the same errors as @stdietrich had |
Hello,
We notice a weird issue where if we fetch a gem which does not exist on Gemirro, it gets fetched fine from Rubygems.org and also gets served to the client. However the index_update seems to fail (https://github.com/PierreRambaud/gemirro/blob/master/lib/gemirro/server.rb#L151). Any new gem fetches after this point fail until the server is restarted. When server is restarted, again it works for 1 new fetch, but index update fails and so on.
The text was updated successfully, but these errors were encountered: