bugout-dev

humbug

Python2021–2021

bugout-dev / humbug

humbug

Get usage metrics and crash reports for your API, library, or command line tool.

Explore on GitHub Read Hacker News discussions

2Distinct people

4Mentions

0Explicit recommenders

37GitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

Get usage metrics and crash reports for your API, library, or command line tool.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week4 dated mentions

Observed mentions: 2021-03-19 00:06:46 UTC to 2021-07-08 10:41:12 UTC. Weeks start Monday, UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Submissions	Comments
Mar 15	2021-03-15 00:00:00 UTC	2021-03-22 00:00:00 UTC	1	1	0
Mar 22	2021-03-22 00:00:00 UTC	2021-03-29 00:00:00 UTC	0	0	0
Mar 29	2021-03-29 00:00:00 UTC	2021-04-05 00:00:00 UTC	1	1	0
Apr 5	2021-04-05 00:00:00 UTC	2021-04-12 00:00:00 UTC	0	0	0
Apr 12	2021-04-12 00:00:00 UTC	2021-04-19 00:00:00 UTC	0	0	0
Apr 19	2021-04-19 00:00:00 UTC	2021-04-26 00:00:00 UTC	0	0	0
Apr 26	2021-04-26 00:00:00 UTC	2021-05-03 00:00:00 UTC	0	0	0
May 3	2021-05-03 00:00:00 UTC	2021-05-10 00:00:00 UTC	0	0	0
May 10	2021-05-10 00:00:00 UTC	2021-05-17 00:00:00 UTC	0	0	0
May 17	2021-05-17 00:00:00 UTC	2021-05-24 00:00:00 UTC	0	0	0
May 24	2021-05-24 00:00:00 UTC	2021-05-31 00:00:00 UTC	0	0	0
May 31	2021-05-31 00:00:00 UTC	2021-06-07 00:00:00 UTC	0	0	0
Jun 7	2021-06-07 00:00:00 UTC	2021-06-14 00:00:00 UTC	0	0	0
Jun 14	2021-06-14 00:00:00 UTC	2021-06-21 00:00:00 UTC	0	0	0
Jun 21	2021-06-21 00:00:00 UTC	2021-06-28 00:00:00 UTC	0	0	0
Jun 28	2021-06-28 00:00:00 UTC	2021-07-05 00:00:00 UTC	0	0	0
Jul 5	2021-07-05 00:00:00 UTC	2021-07-12 00:00:00 UTC	2	0	2

What Hacker News says

4 sources

zomglings·Jul 8, 2021

Thanks for looking at the code, and for your feedback! Here is a recipe for adding error reporting (reporting of all uncaught exceptions) in a Python project. The highlighted line shows that, when you instantiate a reporter, you have to pass a consent mechanism: https://github.com/bugout-dev/humbug/blob/main/python/recipe... We allow you to create a consent mechanism that always returns true: > consent = HumbugConsent(True) But even with that mechanism, we ultimately respect BUGGER_OFF=true: https://github.com/bugout-dev/humbug/blob/main/python/humbug... Of course, someone can always create their own subclass of HumbugConsent which overrides that check. We don't have a good way to prevent this, nor would we want to restrict anyone's freedom to modify code. re: Kaggle and stack trace deidentification We started by crawling public GitHub is

Read the rest

sues for Python stack traces and built up a decent sized dataset of these: https://www.kaggle.com/simiotic/python-tracebacks Our emphasis is on building simple programs that we can reasonably expect to run on any reasonable client without using an exorbitant amount of CPU or memory. For this reason, we aren't using black box ML models. Rather, we analyzed the data and came up with some simple regex based rules on how to deidentify stack traces for our v1 implementation. We are in the process of doing this for more languages and building this into a proper deidentification library that can be imported into any runtime - Python + Javascript + Go + etc. Apologies for the link not working. It seems I had to publish a version of the notebook. This link should work now: https://www.kaggle.com/simiotic/python-tracebacks-redactor Actually, we started this work on a livestream if you're interested in watching: https://youtu.be/TFKe614Ml1M Again, really appreciate your engagement and feedback. Thank you!

In Console Do Not Track – Proposal for a standard environment variable

zomglings·Jul 6, 2021

Happy to show you some code. You cannot set up Bugout telemetry in your codebase without first defining your consent flow. We have a library of consent mechanisms that you can chain together like lego blocks to build these flows. For example, our Python consent library is here: https://github.com/bugout-dev/humbug/blob/main/python/humbug... Consent is calculated at the time that each reports are sent back. This means that your users can grant and revoke their consent on a per-report basis, which is the only respectful way to do things. We are also building programs which will deidentify reports on the client side, before any data is even sent back to our servers. This work is still in the early stages, but here's v0.0.1 of the Python stack trace deidentifier: https://www.kaggle.com/simiotic/python-tracebacks-redactor/e... Besides Python,

Read the rest

we also support Javascript, Go, and we added Java support last week. I would really love to hear any feedback you have.

In Console Do Not Track – Proposal for a standard environment variable

pahita·Mar 31, 2021Submission

Show HN: Bugout.dev – Crash and usage reports for developer tools

Hello everyone, I’m Sophia, founder of Bugout.dev. I started off as a professional ballerina, and entered technology later in my working life - through the OpenAI Scholars program. My co-founder, Neeraj (zomglings on HN), is a mathematician and now programmer. When I was learning how to code I kept running into issues. I found Stackoverflow and GitHub issues hard to navigate, often leading me to outdated solutions to the problems I was experiencing. That experience made me want a product that would collect crashes and immediately let the creators of the software I was using know about the issue. And when they or their community had fixed the issue, they could notify me about that and direct me to a public site detailing the solution. Over time, this idea evolved and resulted in Bugout.dev. Bugout makes it easy for creators of developer to

Read the rest

ols to collect usage metrics and crash reports from their users. This applies equally well to libraries, command line utilities, and APIs. We're advocates of ethical data collection, and all reports are collected with clear user consent. Maintainers can also comply with GDPR requests for access and deletion with a single API call each. We are also building a public knowledge base of issues and solutions from open source projects. We were inspired by rustc error messages in this and how they point users to documentation that can help you resolve compiler errors. Projects integrating with Bugout can link users to the knowledge base using a search query, which allows them to direct users to solutions customized to operating system, library version, and even compiler/runtime version. We support developer tools written in Python and in Go - we just launched the Go library this week! Please check out our GitHub page: https://github.com/bugout-dev/humbug. We would greatly appreciate your feedback.

8 points · Open discussion

zomglings·Mar 19, 2021Submission

Show HN: Usage and crash reports for Python libraries and command line tools

Understanding how your users experience your software is always difficult. It is especially difficult if we're talking about a developer tool like a library or command line utility. Devtool maintainers have to rely on GitHub issues and IRC/Slack/Discord to talk with their users. They miss out the experience of the majority of their users, who never build up the motivation to create an issue or post a message on Slack. Humbug addresses this problem. It collects developer tool usage reports and crash reports in a principled manner, only with the end user's full consent. Individuals or teams that maintain developer tools can use these reports to identify issues in their software, prioritize features, and in general improve their users' experience. You can find a lot more information on GitHub: https://github.com/bugout-dev/humbug Here is a s

Read the rest

hort YouTube video showing how Humbug works: https://www.youtube.com/watch?v=-k2c8o_sXC4 Humbug is free to use for small projects. I hope you find it useful. If you would like to discuss your use case in greater detail, I would love to speak with you in the comments. You can also reach me by email (check my profile).

4 points · Open discussion