Bugsnag Blog

Bugsnag - San Francisco, CA https://bugsnag.com We're helping software teams focus on building great software by building automated crash monitoring for web and mobile apps. Half of a typical developer’s time is currently spent finding and fixing bugs; we aim to bring that number as close to zero as possible, by automating the entire error monitoring process. * Lead Operations Engineer - https://jobs.lever.co/bugsnag/96421958-f597-46e3-b12e-ae2184bad43f * Lead Frontend Engineer - https://jobs.lever.co/bugsnag/72d44059-903c-4e7c-b064-6eb89c13fce2 We already work with some of the world's fastest growing companies like Square, GitHub, Mashable, Goodreads, Buffer, Heroku (and thousands more). We’re currently doubling revenue every few months and we're now expanding our team. Email me (james at bugsnag.com) to talk more!

Bugsnag (https://bugsnag.com) is hiring! We're building automated crash detection for web and mobile apps. We're a team of software developers building tools for software developers. Our product is built around what would be an amazing product for us and our customers to use. Currently we're looking for full-stack engineers and an enterprise salesperson, to join our team of 6 people. Email me at [email protected] to talk more!

There seems to have been an explosion in error monitoring apps recently, competition in this market is great. If you are checking out other services, our product Bugsnag (https://bugsnag.com) looks pretty similar to raygun, with more platforms supported, chat/sms notification and automatic issues/ticket creation.

Bugsnag (SmartBear) | Android SDK Engineer | Full time | Onsite (Bath, UK) or Remote (UK) | https://bugsnag.com/ Cross platform crash-reporting and application stability dashboard. We're looking for an experienced Android engineer to join our open source team and help maintain our Android SDKs - used by engineering teams worldwide including some of the biggest names in tech. Work with a team of diversely-skilled engineers in an ever-increasing number of technologies and frameworks, including React Native, Unity and Unreal Engine. For more information see: https://smartbear.com/company/careers/job-post/?gh_jid=4901125003

Also please don't use bad fonts. Someone posted the following article the other day and the font drove me so nuts that I had to resort editing the CSS code to make it readable. https://blog.bugsnag.com/bug-day-race-condition-therac-25/ I really wish "reading mode" was a prominent feature in desktop browsers.

CoffeeScript was great, and I'm pleased how relatively easy it's been to move away from it now that ES6 offers most of the same benefits. I've recently started moving our existing CoffeeScript + React codebase – it's been okay, though I still miss the terse CoffeeScript syntax. A similar blog post that's helped is Bugsnag's: https://blog.bugsnag.com/converting-a-large-react-codebase-from-coffee…

Another error tracking system for your list: https://bugsnag.com/ It has been rock solid for us with no event limits and cheap pricing. (not an employee, just a fan)

After trying a few alternatives, I've settled on https://bugsnag.com

+1 for Sentry. This is what we use at work. For the side business I work (https://styleci.io) we use Bugsnag; https://bugsnag.com and a custom application.

http://bugsnag.com automatically translates error messages using source maps.

Thanks! Hopefully 500 errors would never occur of course, but in that case I'd just return: { error: "Internal server error, please try again later" } There's not really a reason to give away anything else, it's usually because something is broken (database connection and whatnot) and the developers are probably already aware of it with tools such as Bugsnag[1] and alike. In general for error messages, exceptions should be handled gracefully and output a simple message that is understandable for the user. It might also be ideal to include an error code with the JSON response if you have a lot of different error messages that happens under the same HTTP status code (e.g. 400 Client Error). [1] https://bugsnag.com

Bugsnag (https://bugsnag.com) supports Rails, PHP, Python/Django, Nodejs, Android, iOS and Unity. Caveat: I'm a founder there.

Hey, thanks for the kind words. I hadn't really planned to share this project today, which is why there's no mention of privacy on the site. To answer your question: all of the "computation" is done client-side, but depending on which features you use, the client might ask the server for data at a word level (like "give me all the rhymes of 'trust'" or "how many syllables are in 'privacy'"), so I guess in a sense your text can be sent to the servers, but never in an aggregated way. Also, as someone who also cares about privacy, I can tell you: - I don't keep any server logs - The only tracking I do (to get traffic numbers) is self-hosted and uses Fathom[1] (which respects privacy in a variety of ways) - I jump through a fair number of hoops to prevent the other third-party tools (Bugsnag[2] and Appzi[3]) from collecting personally identifiable information While the details of the above might change at some point (I may eventually add some basic server logging, for example), the spirit will not. I don't want to collect any data that I don't absolutely need. Hope that's helpful! [1]: https://usefathom.com [2]: https://www.bugsnag.com [3]: https://www.appzi.com

Bugsnag | Customer Success Manager | San Francisco, CA | Full-time - ONSITE Apply here: https://jobs.lever.co/bugsnag/1b9e1ed6-fa72-4105-ac28-e1c66fa286d2 Bugsnag | Software Engineer, Customers | San Francisco, CA | Full-time - ONSITE Apply here: https://jobs.lever.co/bugsnag/8f41b0d1-becb-4054-b2d3-e26ee4ec27a0 All Roles: https://jobs.lever.co/bugsnag Website: https://www.bugsnag.com/ Bugsnag helps teams focus on building better software by providing automated crash monitoring for web, mobile, desktop, and server apps. Currently, half of a typical developer’s time is spent finding and fixing bugs; we aim to bring that number as close to zero as possible by automating the entire monitoring process and allowing developers to focus their time on feature development. To do this, we give our users instant visibility into where their code is not executing as expected, we then measure these errors, collect all related data, and give our users the information they need to understand which software issues really matter and need fixing.

Bugsnag | San Francisco AND Bath, UK | https://www.bugsnag.com/ | Full-time | Onsite About us: Bugsnag helps teams focus on building better software by providing automated crash monitoring for web, mobile, desktop, and server apps. Currently, half of a typical developer’s time is spent finding and fixing bugs; we aim to bring that number as close to zero as possible by automating the entire monitoring process and allowing developers to focus their time on feature development. To do this, we give our users instant visibility into where their code is not executing as expected, we then measure these errors, collect all related data, and give our users the information they need to understand which application errors really matter and need fixing. Open Roles: - Director of Infrastructure (in both Bath and UK) - Senior Platforms Engineer - Front End Software Engineer If interested, please visit our careers page and apply - https://jobs.lever.co/bugsnag *Please include a short note mentioning you saw this posting on HN.

https://www.bugsnag.com/blog/bug-day-460m-loss/ It made me laugh! And cry inside

> Europeans I have mentioned this to considered what did happen a sensible outcome. Well, yeah. The firmware had been designed for a quite different rocket, the Ariane 4: https://www.bugsnag.com/blog/bug-day-ariane-5-disaster I don't know how this is really a mark against Ada, it's an issue that would only be discovered by human intervention or by running a simulation of the rocket.

Or Arianne 5[0] Both had code reviews. Both catastrophically failed. No I am not trying to draw causation that code reviewed software ends in tragedy :) [0]: https://www.bugsnag.com/blog/bug-day-ariane-5-disaster

> If the rules say to abort, the software aborts. Humans get to say "I think we'll be fine", and put lives on the line. But logic errors and bugs in "thoroughly-tested" (subjective, determined by humans/corporations) software-controlled systems kills too. Interesting thought experiment: How many humans will die in 2031, across all industries, because of bad software? https://www.bugsnag.com/blog/bug-day-race-condition-therac-25

This is a really nice idea but considering we haven't even solved the relatively simple case of users giving permissions to apps and expecting them to behave responsibly, I'm not optimistic that we can solve the much more challenging case of importing library code. e.g., If someone gives an app the ability to upload photos, it can silently read all photo metadata, upload all photos to a private server instead of uploading just the single photo that the user picked. This can be solved with OS level standard photo pickers but it hasn't been yet. Same with package code. Maybe a package needs network access for stuff it genuinely needs to do. However it can (and probably will) at some point go above and beyond in the amount of data it collects. FB Mobile SDK outage is a good example of this. https://www.bugsnag.com/blog/sdks-should-not-crash-apps

Technically that has happened: https://www.bugsnag.com/blog/bug-day-race-condition-therac-25 But you're right, software bugs don't generally result in lives lost, at least directly.

$1B is a high bar, but there are probably examples. Another comment mentions MCAS, but maybe that's too easily classified as a management failure. Out of curiosity I looked up a couple of other contenders, but neither made the cut. However, that search took me to an example that I didn't recall, resulting in loss of life. I'll probably reference this story about the Therac-25 in the future as it hits on a number of clear software engineering failures: -- https://www.bugsnag.com/blog/bug-day-race-condition-therac-25

I will leave this right here for your education - https://www.bugsnag.com/blog/bug-day-ariane-5-disaster

Code reuse can result in failures. Sometimes those failures are big and loud. The Ariane 5 failure also happened in 1996, which is quite funny. :) https://www.bugsnag.com/blog/bug-day-ariane-5-disaster https://www.youtube.com/watch?v=gp_D8r-2hwk

re: the actual bug - it took a long time for people to reproduce it and figure out what it was. This article gives an overview of the bug: https://www.bugsnag.com/blog/bug-day-race-condition-therac-25 A much longer paper about the system here (linked from the OP twitter thread) https://web.stanford.edu/class/cs240/old/sp2014/readings/therac-25.pdf

If I recall correctly, the erroring code originated from the Ariane 4, where it was required to align the vehicle after launch. It was a bit of a perfect storm: the code was left in for diagnostic purposes, a steeper trajectory in the Ariane 5 triggered the bug, and the system had supposedly been battle-tested in Ariane 4. It's been a while but I wrote about this here: https://blog.bugsnag.com/bug-day-ariane-5-disaster/

Some more resources for learning more about tmux: - The Tao of tmux [0] - A minimalist guide to tmux [1] - Benefits of using tmux [2] - tmux shortcuts & cheatsheet [3] [0] https://leanpub.com/the-tao-of-tmux/read [1] https://medium.com/actualize-network/a-minimalist-guide-to-tmux-13675f… [2] https://blog.bugsnag.com/benefits-of-using-tmux/ [3] https://gist.github.com/MohamedAlaa/2961058

Every time I see a race condition like this the only thing I can think of is the Therac-25: https://blog.bugsnag.com/bug-day-race-condition-therac-25/ This isn't that, obviously, but it underscores the importance of testing. This clearly should have been caught in QA.

Also, just saw this (see below), another example of JS injection using CodePush (by MSFT) and RN, Apple seems to fine with this....doesn't this have them same security issue? https://blog.bugsnag.com/react-native-plus-code-push/

We have been meaning to get around to looking into this on my current project but haven't yet: I believe the browser's error event will return a column number. > Column numbers in Firefox. Firefox is the only browser that doesn't support column numbers for exceptions. This makes debugging minified javascript essentially impossible. I've sent one patch but there's a lot more to do. https://bugsnag.com/blog/js-stacktraces/ - written in 2014 but MDN now says: > Column number for the line where the error occurred (number) - Requires Gecko 31.0 https://developer.mozilla.org/en-US/docs/Web/API/GlobalEventHandlers/o… If anybody has live experience with this, I'm eager to hear about it.