HackerTrans
TopNewTrendsCommentsPastAskShowJobs

abhinavg

no profile record

Submissions

Anthropic builds Rust support for ConnectRPC

github.com
4 points·by abhinavg·4 mesi fa·0 comments

Yay – Yet Another YAML

kriskowal.com
3 points·by abhinavg·5 mesi fa·0 comments

git-spice: open-source stacking CLI for GitHub and GitLab

abhinav.github.io
3 points·by abhinavg·9 mesi fa·0 comments

Show HN: git-spice, Git branch and PR stacking tool

abhinav.github.io
3 points·by abhinavg·2 anni fa·0 comments

Show HN: Error return traces for Go, inspired by Zig

github.com
133 points·by abhinavg·3 anni fa·84 comments

Designing Go Libraries: The Talk: The Article

abhinavg.net
1 points·by abhinavg·4 anni fa·0 comments

comments

abhinavg
·6 mesi fa·discuss
If you’re interested in exploring tooling around stacked PRs, I wrote git-spice (https://abhinav.github.io/git-spice/) a while ago. It’s free and open-source, no strings attached.
abhinavg
·3 anni fa·discuss
The README covers the idea behind errtrace in more details, but the primary difference is in what is captured:

pkg/errors captures a stack trace of when the error occurred, and attaches it to the error. This information doesn't change as the error moves through the program.

errtrace captures a 'return trace'--every 'return' statement that the error passes through. This information is appended to at each return site.

This gives you a different view of the code path: the stack trace is the path that led to the error, while the return trace is the path that the error took to get to the user.

The difference is significant because in Go, errors are just plain values that you can store in a struct, pass between goroutines etc. When the error passes to another goroutine, the stack trace from the original goroutine can become less useful in debugging the root cause of the error.

As an example, the Try it out section (https://github.com/bracesdev/errtrace/#try-it-out) in the README includes an example of a semi-realistic program comparing the stack trace and the return trace for the same failure.
abhinavg
·3 anni fa·discuss
Thanks! No, just one of the maintainers with a free evening.
abhinavg
·3 anni fa·discuss
I'm a happy duck.com address user. I can answer these questions:

What it is: It gives you private throwaway email addresses. Instead of signing up for a website with <real>@gmail.com, use <fixed>@duck.com. It will forward the email to <real>@gmail.com after removing any trackers from it. It also lets you generate <random>@duck.com addresses on demand. If you sign up for something with <random>@duck.com, and they start spamming you, you can turn the email address off without doing anything to <real>@gmail.com or <fixed>@duck.com.

How to re-access it: Information about your duck.com address is stored in that browser. If you use the Browser extension, that remembers it. You simply need to log into that email address from your current browser. To do this, visit https://duckduckgo.com/email/, click on "I already have a Duck address", and enter your original <fixed>@duck.com address. It will email you a one-time password to <real>@gmail.com, and you'll be back in again.