Currently (2017/07/14 13:08 JST), https://www.stackage.org/lts-8.22/hoogle?q=%5Ba%5D returns an error message "The given Hoogle database is not available."
It seems any query and lts version of hoogle returns the same error.
We just updated the stackage-server version, and the cron job is still
lagging behind. This should hopefully be resolved in the next few hours.
On Fri, Jul 14, 2017 at 7:09 AM, Yuji Yamamoto notifications@github.com
wrote:
Currently (2017/07/14 13:08 JST), https://www.stackage.org/lts-
8.22/hoogle?q=%5Ba%5D returns an error message "The given Hoogle database
is not available."
It seems any query and lts version of hoogle returns the same error.—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/fpco/stackage/issues/2647, or mute the thread
https://github.com/notifications/unsubscribe-auth/AADBBxXRI3-ijh2c_87gub39biJfNI4xks5sNuoJgaJpZM4OXzpQ
.
OK, should be fixed, thanks for the notification on this. Older databases are still being regenerated, but lts-8.22 is up and running.
Confirmed it works! Thank you!
Most helpful comment
We just updated the stackage-server version, and the cron job is still
lagging behind. This should hopefully be resolved in the next few hours.
On Fri, Jul 14, 2017 at 7:09 AM, Yuji Yamamoto notifications@github.com
wrote: