HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
juju
errgo
Go2014–2014
juju / errgo

errgo

Error tracing and annotation.

Explore on GitHubRead Hacker News discussions
2Distinct people
2Mentions
0Explicit recommenders
229GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Error tracing and annotation.

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 day2 dated mentions

Observed mentions: 2014-05-13 00:19:00 UTC to 2014-06-04 17:16:13 UTC.

012014-05-13 00:00:00 UTC to 2014-05-14 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMay 132014-05-14 00:00:00 UTC to 2014-05-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-05-15 00:00:00 UTC to 2014-05-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-05-16 00:00:00 UTC to 2014-05-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-05-17 00:00:00 UTC to 2014-05-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-05-18 00:00:00 UTC to 2014-05-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-05-19 00:00:00 UTC to 2014-05-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-05-20 00:00:00 UTC to 2014-05-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-05-21 00:00:00 UTC to 2014-05-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-05-22 00:00:00 UTC to 2014-05-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-05-23 00:00:00 UTC to 2014-05-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-05-24 00:00:00 UTC to 2014-05-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMay 242014-05-25 00:00:00 UTC to 2014-05-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-05-26 00:00:00 UTC to 2014-05-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-05-27 00:00:00 UTC to 2014-05-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-05-28 00:00:00 UTC to 2014-05-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-05-29 00:00:00 UTC to 2014-05-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-05-30 00:00:00 UTC to 2014-05-31 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-05-31 00:00:00 UTC to 2014-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-06-01 00:00:00 UTC to 2014-06-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-06-02 00:00:00 UTC to 2014-06-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-06-03 00:00:00 UTC to 2014-06-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-06-04 00:00:00 UTC to 2014-06-05 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJun 4

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.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
May 132014-05-13 00:00:00 UTC2014-05-14 00:00:00 UTC101
May 142014-05-14 00:00:00 UTC2014-05-15 00:00:00 UTC000
May 152014-05-15 00:00:00 UTC2014-05-16 00:00:00 UTC000
May 162014-05-16 00:00:00 UTC2014-05-17 00:00:00 UTC000
May 172014-05-17 00:00:00 UTC2014-05-18 00:00:00 UTC000
May 182014-05-18 00:00:00 UTC2014-05-19 00:00:00 UTC000
May 192014-05-19 00:00:00 UTC2014-05-20 00:00:00 UTC000
May 202014-05-20 00:00:00 UTC2014-05-21 00:00:00 UTC000
May 212014-05-21 00:00:00 UTC2014-05-22 00:00:00 UTC000
May 222014-05-22 00:00:00 UTC2014-05-23 00:00:00 UTC000
May 232014-05-23 00:00:00 UTC2014-05-24 00:00:00 UTC000
May 242014-05-24 00:00:00 UTC2014-05-25 00:00:00 UTC000
May 252014-05-25 00:00:00 UTC2014-05-26 00:00:00 UTC000
May 262014-05-26 00:00:00 UTC2014-05-27 00:00:00 UTC000
May 272014-05-27 00:00:00 UTC2014-05-28 00:00:00 UTC000
May 282014-05-28 00:00:00 UTC2014-05-29 00:00:00 UTC000
May 292014-05-29 00:00:00 UTC2014-05-30 00:00:00 UTC000
May 302014-05-30 00:00:00 UTC2014-05-31 00:00:00 UTC000
May 312014-05-31 00:00:00 UTC2014-06-01 00:00:00 UTC000
Jun 12014-06-01 00:00:00 UTC2014-06-02 00:00:00 UTC000
Jun 22014-06-02 00:00:00 UTC2014-06-03 00:00:00 UTC000
Jun 32014-06-03 00:00:00 UTC2014-06-04 00:00:00 UTC000
Jun 42014-06-04 00:00:00 UTC2014-06-05 00:00:00 UTC101

What Hacker News says

2 sources
NateDad·Jun 4, 2014
There are a lot of error handling libraries out there. On Juju, we're working on one right now. This is the preliminary version: https://github.com/juju/errgo Basically you just call a function every time you would return an error, and it automatically records the file and line number and lets you add on some context to the message, plus it gives you the option to mask the type of the error (to hide implementation details from your callers). I wouldn't use errgo right now, it's still under heavy development, but it's similar to a lot of other error handling libraries out there.
In Go error handling

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.