-
Notifications
You must be signed in to change notification settings - Fork 117
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
add stats aggregation #177
Conversation
Looks like Travis timed out one of the builds, all others passed all tests etc so I'm pretty sure it's fine |
I've restarted that build. Seems like the larger your built matrix the more likely you'll end up getting a rotten Travis run. |
OK, build passing, FYI I am currently using this in prod, working well, I just want to get rid of the bloodhound fork in my app asap :) |
LGTM 👍 , @bitemyapp ? |
Has a test, looks pretty compact. I'll merge. |
Thanks guys, @bitemyapp when will the next version be released to hackage? |
@shmish111 when either myself or @MichaelXavier feel like it. What's the rush? You can add bab3565 to your |
@bitemyapp I did not know you could do that, it's pretty cool. |
@bitemyapp using a git location is bloody hell, stack wants to recompile all the time for no apparent reason and bloodhound is slooooow at compiling. A release would be very much appreciated as it would make our lives so much more pleasant :-) |
@shmish111 mark it This won't be the last library you'll have a git dep on if you're using Haskell at work. Might as well learn how to make it work. |
@bitemyapp |
Could you elaborate or provide an example? Sounds like something that should get filed as a bug on commercialhaskell/stack too. |
I should have some time today to put together a changelog and cut a release. |
@MichaelXavier I'll get it, I want to take care of #180 anyway. |
http://hackage.haskell.org/package/bloodhound 0.14.0.0 is up. |
No description provided.