HN user
Sentry.io settled on Clickhouse for error and transaction data after reviewing several options including Citus and Elastic. We've been happy with both the performance and how well it scales from Open Source installs to our SaaS clusters.
Sorry about this -- a schema change during deployment led to a deadlock on the database. We are investigating why our usual tactics failed us here.
For those on Bitbucket, <username>.bitbucket.io is the HTTPS equivalent of <username>.bitbucket.org.
We try to encourage others to do those sorts of features via add-ons (http://blog.bitbucket.org/2015/12/29/file-viewer-for-bitbuck...).
Public (Open Source) repositories on Bitbucket do not have a limit to the number of contributors.
We're very focused on professional teams working on private projects -- but you can't see that because they're all private. Bitbucket is sort of like an iceberg: 1. you can only see a small percentage of the of the total mass; 2. it is blue.
Yes, we're part of Atlassian and we're hiring in San Francisco.
No too much load, really. We (Bitbucket) already have pre-receive hooks for a handful of other things. The trick would be defining the rules properly to have a reasonably low false negative rate while avoiding work inhibiting false positives (or allow for a mechanism to override it with, say, a force push).
Of course, 93% of our repositories are private so this feature may not be exceedingly useful to our customers vs other things we could be spending our time on.
Edit: I shouldn't have said not useful, rather, comparatively there may be more value in us pursuing other work first. E.g., provide a mechanism for 3rd party pre-receive hooks via our add-on system.
The developer documentation is here for anyone interested in developing their own Bitbucket add-on projects.
Just speaking for myself here, but, enabling the use of SourceTree as a VS extension would be pretty slick. Perhaps open sourcing the lower levels of abstraction so other projects like the one above could collaborate. There's surely plenty of work to do to enable that so I'm not sure if I'd expect to see anything like that any time soon.
If you like Bitbucket don't feel bad about using it. We like seeing real developers benefit from our efforts -- it's a refreshing break from playing cat and mouse with the bad actors trying to ruin it for everyone.
That is one of many reasons why we are hiring. A dozen people can only do so much and we're looking for smart people with new ideas to help us start accelerating the development of BB.
Layer one is for connection pooling on the application servers, layer two (on the database server) is mostly for control purposes.
That's unrelated and is for a networking change we plan to make - and had already planned to make prior to this evening's database nonsense.
Its successor, Robot Odyssey (http://en.wikipedia.org/wiki/Robot_Odyssey), was great. It was the inspiration to create a programming game as a distraction for users during the bitbucket migration a couple of months ago.
I'd link to the bitbucket game but that's too much self promotion for a Saturday.
Edit: s/it's/its/ -- I know better.
I got sign-off to release the code as an Atlassian open source project. I'm hoping someone will want to make it better.