Hacker News: broken_broken_

Optimization tales with CockroachDB: the slow logout

broken_broken_ — Wed, 01 Jul 2026 15:30:59 +0000

Article URL: https://gaultier.github.io/blog/optimization-tales-cockroachdb-part2-slow-logout.html

Comments URL: https://news.ycombinator.com/item?id=48748528

Points: 1

# Comments: 0

Optimization tales with CockroachDB: the slow password reset flow

broken_broken_ — Tue, 30 Jun 2026 12:06:23 +0000

Article URL: https://gaultier.github.io/blog/optimization-tales-cockroachdb-part1.html

Comments URL: https://news.ycombinator.com/item?id=48731515

Points: 2

# Comments: 0

I sped up the test suite by 2x with one simple change

broken_broken_ — Mon, 15 Jun 2026 07:29:21 +0000

Article URL: https://gaultier.github.io/blog/I_sped_up_the_test_suite_by_x2.html

Comments URL: https://news.ycombinator.com/item?id=48537771

Points: 2

# Comments: 0

New comment by broken_broken_ in "Tracing Goroutines in Realtime with eBPF"

broken_broken_ — Mon, 06 Apr 2026 06:26:41 +0000

It depends how much the code uses manually spawned goroutines, and how complex the lifecycle of these goroutines is… in big codebases such as kubernetes, docker, etc, it has been a problem. There have been research papers and blogs about this, but most Go developers are not aware of this issue it seems.

New comment by broken_broken_ in "Tracing Goroutines in Realtime with eBPF"

broken_broken_ — Sun, 05 Apr 2026 16:42:25 +0000

Interesting to see an ebpf approach to this idea, some time ago I did the same with Dtrace: https://gaultier.github.io/blog/detecting_goroutine_leaks_wi...

However I did not think of observing the ‘castgstatus’ runtime function.

Always nice to be able to compare the DTrace and Ebpf approaches, they both have different strong points.

New comment by broken_broken_ in "Simple, fast and open-source PHP framework frozen in C-extension"

broken_broken_ — Mon, 16 Mar 2026 14:31:00 +0000

The name clashes with a similar project that has existed for decades: https://zeroc.com/ice

The production bug that made me care about undefined behavior

broken_broken_ — Sat, 27 Dec 2025 18:28:06 +0000

Article URL: https://gaultier.github.io/blog/the_production_bug_that_made_me_care_about_undefined_behavior.html

Comments URL: https://news.ycombinator.com/item?id=46403969

Points: 1

# Comments: 0

Detecting Goroutine Leaks with DTrace

broken_broken_ — Mon, 22 Dec 2025 18:40:46 +0000

Article URL: https://gaultier.github.io/blog/detecting_goroutine_leaks_with_dtrace.html

Comments URL: https://news.ycombinator.com/item?id=46357214

Points: 2

# Comments: 0

New comment by broken_broken_ in "I got hacked: My Hetzner server started mining Monero"

broken_broken_ — Thu, 18 Dec 2025 09:00:44 +0000

I am not an expert in incident reaction, but I thought the safe way was to image the affected machine, turn it off, take a clean machine, boot a clean OS image with the affected image mounted read only in a VM, and do the investigation like that ?

Assume that the malware has replaced system commands, possibly used a kernel vulnerability to lie to you to hide its presence, so do not do anything in the infected system directly ?

New comment by broken_broken_ in "A kernel bug froze my machine: Debugging an async-profiler deadlock"

broken_broken_ — Tue, 16 Dec 2025 07:40:28 +0000

Nice article, thank you. Did you also consider using bpftrace while debugging?

I do not have much experience with it, but I think you can see the kernel call stack with it and I know you can also see the return value (in eax). That would be less effort than qemu + gdb + disabling kernel aslr, etc.

New comment by broken_broken_ in "A million ways to die from a data race in Go"

broken_broken_ — Tue, 25 Nov 2025 07:48:02 +0000

Author here, thanks for the feedback on legibility, I have now just learned about the CSS `tab-size` property to control how much space tabs get rendered with. I have reduced it, should be better now.

A million ways to die from a data race in Go

broken_broken_ — Mon, 24 Nov 2025 07:31:58 +0000

Article URL: https://gaultier.github.io/blog/a_million_ways_to_data_race_in_go.html

Comments URL: https://news.ycombinator.com/item?id=46031319

Points: 4

# Comments: 0

How to reproduce and fix an I/O data race with Go and DTrace

broken_broken_ — Thu, 02 Oct 2025 08:28:24 +0000

Article URL: https://gaultier.github.io/blog/how_to_reproduce_and_fix_an_io_data_race_with_dtrace.html

Comments URL: https://news.ycombinator.com/item?id=45447407

Points: 1

# Comments: 0

Observe live SQL queries in Go with DTrace

broken_broken_ — Sat, 13 Sep 2025 15:28:12 +0000

Article URL: https://gaultier.github.io/blog/observe_sql_queries_in_go_with_dtrace.html

Comments URL: https://news.ycombinator.com/item?id=45232869

Points: 3

# Comments: 0

New comment by broken_broken_ in "Lessons learned from implementing SIMD-accelerated algorithms in pure Rust"

broken_broken_ — Fri, 15 Aug 2025 06:32:00 +0000

I love a good SIMD article!

Just one point about testable assembly: I like the Golang guidelines which require to write a Go version before implementing the same in assembly. That way there is a baseline to compare with in terms of correctness and performance. Also the Go project has recently introduced mutation testing and test coverage on assembly code which is very interesting.

Finally about detecting at runtime the presence of simd: I am confused why a third-party dependency or even the std is needed. At least on x64, it’s just one instruction (“cpuid”) and then checking if a bit is set, right?

New comment by broken_broken_ in "A subtle bug with Go's errgroup"

broken_broken_ — Sat, 09 Aug 2025 18:00:01 +0000

Your are right about shadowing: I just checked and the go specification calls it “redeclaration” and it works as you described:

> Redeclaration does not introduce a new variable; it just assigns a new value to the original

I added a mention about that in the article. Thank you.

A subtle bug with Go's errgroup

broken_broken_ — Sat, 09 Aug 2025 12:20:16 +0000

Article URL: https://gaultier.github.io/blog/subtle_bug_with_go_errgroup.html

Comments URL: https://news.ycombinator.com/item?id=44845953

Points: 27

# Comments: 19

New comment by broken_broken_ in "We shouldn't have needed lockfiles"

broken_broken_ — Wed, 06 Aug 2025 18:09:14 +0000

I agree with the premise, just use a specific version of your dependencies, that’s generally fine.

However: You absolutely do need a lock file to store a cryptographic hash of each dependency to ensure that what is fetched has not been tampered with. And users are definitely not typing a hash when adding a new dependency to package.json or Cargo.toml.

New comment by broken_broken_ in "Ask HN: Have you ever regretted open-sourcing something?"

broken_broken_ — Wed, 06 Aug 2025 05:36:02 +0000

I wrote a toy Kotlin compiler, for fun. Then one day a Jetbrains employee opens an issue which only says: “Why? Just why?”. Maybe it’s the language barrier… but I did not find that particularly polite.

On the other hand I open sourced my blog and received lots of small contributions to fix typos or such which were nice.

New comment by broken_broken_ in "A deep dive into Rust and C memory interoperability"

broken_broken_ — Mon, 04 Aug 2025 19:52:25 +0000

Miri and Valgrind will usually catch this kind of issue. I did lots of work mixing C and Rust and that tripped me as well at the beginning. I wrote about it if someone is interested: https://gaultier.github.io/blog/perhaps_rust_needs_defer.htm...