Brad Fitzpatrick

Hotel captive portal hilarity:

* input type=password for my last name. 🙄
* "Guest not found"

Front desk dude, very apologetic:

* yeah, uh, it has to be only the first 8 letters of your last name
* Oh, and also all lowercase

Of course.

I'd expect nothing less.

Our waiter's name, especially in the all caps on his badge, sounds like a great hacker username: SUBHASH

Or second.

Amalga Distillery in Juneau.

I sat next to one of the owners on a recent flight back from London and said I'd stop by.

Mmm, gin.

After a day at sea en route to Juneau, still hours away, we start to see land.

Kids: "THAT'S Alaska!? Aren't there supposed to be houses?"

CDC is fun. My earlier perkeep.org uses it.

It could save some space but git pack files are pretty decent. Mostly I wanted to be able to git mirror caches around with standard tools.

GitHub - tailscale/gomodfs: GOMODCACHE Go module cache FUSE filesystem GOMODCACHE Go module cache FUSE filesystem. Contribute to tailscale/gomodfs development by creating an account on GitHub.

Here's the code:

github.com/tailscale/go... -- a Go module cache virtual filesystem (FUSE or WebDAV) with deduping

GitHub - tailscale/gomodfs: GOMODCACHE Go module cache FUSE filesystem GOMODCACHE Go module cache FUSE filesystem. Contribute to tailscale/gomodfs development by creating an account on GitHub.

Here's the code:

github.com/tailscale/go... -- a Go module cache virtual filesystem (FUSE or WebDAV) with deduping

We did? How? 😬

Maybe we can fix it.

Surprising!

In any case, the rollout is done now and old IPs are removed.

I looked at your pcap.

Why are you querying without the EDNS option to get a buffer size above 512? 😉

We're in a few day migration period where two sets are included.

It'll shrink soon.

And might shrink further in the future.

But I did look at pcap size of AAAA reply and it fit? Are you seeing otherwise?

Oh hell yeah.

Yeah it seems to work if just ignore the context given to me from go-fuse.

Perhaps my EIO error returns on context canceled are tainting some go-fuse or kernel cache. I didn't think I was setting any validity on those but maybe I was? Will try to make a minimal repro.

I see plenty of INTERRUPT but I don't control the caller. The caller is the Go build system (cmd/go) doing its thing.

(I noticed 2.8.0 exists and tried it too... no change.)

Hey @hanwen.bsky.social‬, under load I'm getting tons of seemingly bogus "context canceled" FUSE errors on both macOS and Linux, breaking operations that callers are still waiting on.

(with hanwen/go-fuse/v2 v2.7.2)

Ring any bells before I start debugging?

I tried -race mode on a whim but nothing

assuming you run it with a go.mod file in a txttar it might already do that (did you know multiple file playground runs are a thing? Few people do)

Maybe the slow part is checking for module updates.

The Go playground should presumably be using Google's internal version of what I'm writing?

I'll have you know that your nerdsnipe resulted in a day of me refabstractoring it all and all my tests passing but weird errors I can't yet explain doing real builds. 🤪

The fight continues.

But then it'll have like 3 backends when released assuming I find this damn bug 😅

A very small git library for just making some pack files of some trees. 😄

go-git has some really big interfaces with many methods used. And doesn't implement the server over all transport types.

I'm also good at using the porcelain after consuming a lot of spicy stuff.

I was forced to learn this horror/trivia about how git sorts its tree objects (for gomodfs), so now you have to too:

news.ycombinator.com/item?id=4458...
(link to a comment I just made there)

Sorry.

We have a Richard Scarry board game even...

Yeah, I should probably make that an interface so people can plug in whatever storage they want. Using git as the content addressable blob storage was just a quick easy hack and what we'd probably use.

It's a bit rich that AWS feels it can clearly communicate these things to LLMs when it's failed for twenty years to do so to customers.

The FIPS 140-3 Go Cryptographic Module Go now has a built-in, native FIPS 140-3 compliant mode.

We announced the new native Go FIPS 140-3 mode today!

FIPS 140, like it or not, is often a requirement, and I was increasingly sad about large deployments replacing the Go crypto packages with non-memory safe cgo bindings.

Go is now one of the easiest and most secure ways to build under FIPS 140.

You can't set docker run -v paths?

Yup. Just testing & cleaning it up first.

It's barely alive.

Toolset to build, run and manage macOS and Linux VMs Native performance. Remote storage for Virtual Machines. Many integrations including GitHub, GitLab and more.

Not having to start your CI build with writing ~1GB of zips to disk (even if it's tmpfs).

Instead, you can share this FUSE filesystem from the host via virtio-fs into containers + QEMU + Tart (tart.run) VM guests, so fresh VMs/containers get a seemingly-full mod cache that they can't write to.