search

docmeta / rubydoc.info

Next generation rdoc.info site
http://rubydoc.info
MIT License
132 stars 43 forks source link

Service unavailable (503) #156

Open sthyregod opened 3 years ago

sthyregod commented 3 years ago

I've been running into a few 503 errors when browsing the site, specifically when trying to browse the documentation on the following link:

https://www.rubydoc.info/github/rails/activeresource

screenshot

whatisdot commented 3 years ago

I also observed this yesterday afternoon (Apr 26).

@lsegal Did the hosting for rubydoc.info change recently?

nateleavitt commented 3 years ago

Also experiencing this with my own gem.

lsegal commented 3 years ago

There was an outage that seemed to be only affecting github projects. We investigated and it should now be resolved. Will be looking into how that happened. Thanks for reporting!

Crusader500 commented 3 years ago

I am having this same issue please fix it

pedrofurtado commented 3 years ago

Still with error 😢

lsegal commented 3 years ago

We ran a quick restart on the service and it should be working now. We had an out of memory error which is pretty abnormal and will be investigating what caused it so we can fix and avoid this in the future.

Thanks for reporting!

whatisdot commented 3 years ago

@lsegal Looks like we're still seeing some disruption: https://rubydoc.info/gems/yard/File

lsegal commented 3 years ago

Thanks again! Made some adjustments just now to the memory usage so we can start working out how to better improve service.

Looks like people are catching this before our own uptime notifications are, so that's something we will also adjust.

lsegal commented 3 years ago

(PS: service is now functioning again)

SampsonCrowley commented 3 years ago

@lsegal down again, right now I'm unable to view the docs for StdLib StringIO

SampsonCrowley commented 3 years ago

@lsegal This seems to come back up with the same problem quite frequently. maybe it is time for a more robust resolution? (not that I have any suggestions without knowing what the original resolutions have been, every issue just says it's "being worked on", or "been fixed")

Very much appreciate the rubydocs service and would be willing to contribute to solving the solution in a more permanent manner if possible

https://github.com/docmeta/rubydoc.info/issues/53 https://github.com/docmeta/rubydoc.info/issues/109 https://github.com/docmeta/rubydoc.info/issues/122 (mentioned, not main issue) https://github.com/docmeta/rubydoc.info/issues/124 https://github.com/docmeta/rubydoc.info/issues/134 https://github.com/docmeta/rubydoc.info/issues/147 https://github.com/docmeta/rubydoc.info/issues/158

whatisdot commented 3 years ago

I share @SampsonCrowley's thoughts. The rubydocs project is a tremendous help for my team and we're willing to help contribute to a solution for this issue.

Duartemartins commented 3 years ago

Getting this error too on the RGL gem.

iloveitaly commented 2 years ago

I'm still running into errors like this as well.

jk779 commented 2 years ago

Its still happening quite often, more 503 then not. If you need help with hosting or the API connection, I'm glad if I can help.

If its an issue with a rate limit by github, which https://github.com/docmeta/rubydoc.info/issues/156#issuecomment-827774478 suggests, maybe they're willing to up the qouta for an open source project that has such a huge audience/impact?

svoop commented 1 year ago

503 have become less frequent, but apparently, docs (most notably generated off GitHub main) are often garbled. I mention it here because it could be a memory issues as mentioned above.

@lsegal YARD is tremendously useful for the community! That said, maybe Ruby Central would be willing to host (or sponsor the hosting) – having more CPU and mem resources for rubydoc.info might help.