@hummingrain Depending on your cup of tea, I know stripe and chef have seattle offices, and I've heard okay stuff about them (though second hand).
Good luck in your search!
I can't decide if I want to write down this thing that isn't on the internet for all to share in, or pass it along by word of mouth only for as long as possible.
Both seem appropriate.
I played a card game with my family called "Sergeant Major" growing up. Years later, I've finally googled this game, and there's definitely a game by that name, but what we played is *not that*.
I could not google-fu my way to a single card game that matches what we played.
I find it so cool and weird that I know a card game rare enough I can't find it online.
Wobscale.social had a redis aof file corruption, which also brought down sidekiq. Your timeline might be missing some things while sidekiq catches up.
tbqh, I'm not sure if it will result in anything being missed or not.
I apologize for the issues, and intend to dig a bit more into how the initial corruption happened.
This is the weirdest pkg-config invocation I've seen: https://github.com/dgrunwald/rust-cpython/blob/0.1.0/python3-sys/build.rs#L278-L282
Yes, I'm reading that code because it didn't work in some case
I think the earliest reference to this solution is here: https://alioth-lists-archive.debian.net/pipermail/bash-completion-devel/2010-May/002743.html, inspired by https://wiki.tcl.tk/1508
What's upvar?
I dunno, what's up with you?
I am now the third fastest person to report a time for Celestial Resort, side B.
Third fastest can also be written as "slowest".
Wow did that take ages to finally beat without dying.
Have you ever wanted AGPL compliance in just one rust macro?
Introducing the "include_repo!" macro, to easily let you compile all your source code into your binary, ready to be served to your users.
Hey everyone, I'm Sam. I'm friends with @ek, @iliana@cybre.space, @noahm@chaos.social, and probably others that I don't yet know in the fediverse. I work on Linux containers for a living. #introduction
For anyone curious about the details, it's basically "ipv6" https://github.com/moby/moby/issues/33099
In go's defence, the behaviour was fixed in go1.9, so it probably can't panic anymore (whoops, didn't realize that until I looked it up now) https://github.com/golang/go/issues/18806
@iliana@cybre.space For bonus points, did you know that the `Addr` may not actually be what it's listening on?
That is to say, the following code can panic in some cases:
conn, err := net.Listen("tcp", ":8080")
if err != nil {
log.Fatal("couldn't listen")
}
_, err = net.Dial("tcp", conn.Addr().String())
if err != nil {
panic("this does happen in some cases")
}
software
Original commit that added it doesn't totally answer why it exists, but I guess it's the best I'll get for now. It was a lot shorter back then too!
software
@cosine@anticapitalist.party It is amazing and I developed muscle memory for using it...
And then the code scared me too much so I rewrote it in rust, so I use pazi these days (https://github.com/euank/pazi).
I'm looking into the best way to bring fasd's file-path-tracking stuff into pazi too is why I'm reading this code