If you're still following me here, I'm now at @mjg59@nondeterministic.computer and won't be posting here any more.
Former biologist. Actual PhD in genetics. Security at https://aurora.tech, OS security teaching at https://www.ischool.berkeley.edu. Blog: http://mjg59.dreamwidth.org. He/him.
If you're still following me here, I'm now at @mjg59@nondeterministic.computer and won't be posting here any more.
Ok, attempting to transfer to @mjg59@nondeterministic.computer
Love to trust PREPROD USE ONLY
https://yum.repos.intel.com/intel-gpg-keys/GPG-PUB-KEY-INTEL-SW-PRODUCTS.PUB still includes a key called CN=Intel(R) Software Development Products (PREPROD USE ONLY)
@tomlowenthal Oh no
[Posting, 3%]: If you don't like Twitter anymore, there is awesome site called Masterbatedone.
Posting through it only works if you can actually post
Looking at which people I follow have Mastodon accounts and realising that leaving Twitter means leaving behind dead people who I can't bear to unfollow
Committing absolute crimes against WebAuthn and the Okta API, and trying to figure out if I can do the same to AWS
I appreciate that my followers are almost certainly not representative of Twitter as a whole, but 5% of them already seem to follow me on Mastodon which seems like kind of a lot
I have won my first conflict with gazelle, and now move onto my second
Ah ok the fix is to add build_tags = ["foo","bar"] to the go_repository() definition in the workspace config
Which means even when I pass the correct build tags, gcc is being called with the flags set by the wrong build tags, and all the #ifdefs are wrong as a result
Ok so the right thing to do here is to express the tags in the go_binary() target, but what's actually breaking things for me here is that go_repository() has "helpfully" called gazelle and generated a BUILD file that has copts set for the default tags
I didn't want to have to learn how to bend gazelle to my whims, and yet
Absolutely the kind of day where it turns out all my problems are due to overly helpful automation that overrides the things the docs say should do what I want
I suspect that the number of Bazel experts out there is not terribly large, but: I'm hitting https://github.com/bazelbuild/rules_go/issues/3203 - one of the dependencies of a go_library() target needs a specific build tag to work in my environment. Is there any way to do that at the moment?
I'll shortly be attempting to migrate to another instance (theoretically all followers automatically get updated? Exciting times), so a brief #introduction while I'm still on this one - I'm a security developer, Linux contributor, and free software advocate focused on ensuring that people are able to make informed decisions about whether their computers are trustworthy and what software can run on them. I also reverse engineer weird IoT things and tend to find exceedingly strange bugs.
"im not owned! im not owned!!", i continue to insist as i slowly shrink and transform into a miniature Falcon 9 stage 1
I mean let's be realistic it'd probably end up with me just shitposting about Elon buy let's pretend I actually have my shit together