dave bonner @rascalking@octodon.social
systems developer for necsys at the mit media lab. masshole.
It just occurred to me to mention: since Mastodon doesn’t have advertising, check and see if the people running your instance(s) have some way to send them donations to help keep the servers running.
If you can, of course! But even a little bit now and then can help, if as many people do it as possible.
I am not actually an instance administrator or anything; I just want the lights to stay on. And my dollar a month is insufficient by itself.
plus side, i know a lot more about how the ca certs packages are supposed to work on debian. and i know a little more about how java's keystore works.
joy is wasting 2+ hours troubleshooting login issues on your jenkins server, only to discover the github enterprise server your school runs, which you're using as an auth source, is no longer returning the cert chain with its ssl cert.
and then trying to troubleshoot why update-ca-certificates isn't adding the cert you just put in place to the java keystore.
and then just saying fuck it and adding it manually so you can get back to what you were supposed to be doing to begin with.
I was one of the college kids sleeping out overnight to get the front row seats at the Shubert in Boston, thanks to my sister doing it first and getting me hooked. I've seen the play probably a dozen times live. And I can rant at my daughter about it, but I don't think I'll be able to convey what it meant to me at that point in my life.
watching the RENT movie, and I'm thinking about how long I'll have to wait before I can let my kids watch. and then I'm realizing how much I'll have to explain so they have the context to appreciate it. the biggie being how AIDS was a flat-out death sentence when RENT was written.
which then makes me wonder how much of what my folks love i just can't appreciate for lack of context. or at least, for lack of a connection to that context.
i know my 3d printer is an enthusiast's printer, but damn, the maintenance required to keep it in working order is making me less enthusiastic. latest is plastic jammed somewhere either in the nozzle or where the hot-end meets the nozzle. i *so* don't want to do the "heat to X degrees so you can unscrew the nozzle" thing.
ugh. okay, so...user error.
if your server is setting cookies and specifying the domain, your calls to client.get() needs to pass a full url, not just the path. and the domains need to match, just like for a regular browser.
for some reason i was assuming the test client would just ignore the domain rules for a browser.
having one of those days where i'm fighting my tools and ready to scream.
for some reason, flask's test client doesn't provide easy access to cookies. neither does the response object it returns.
forgot to mention this earlier, but the media lab is hosting an event celebrating defiance, including the presentation of the lab's first disobedience award. details and link to a live webcast can be found at
ansible's git module is apparently really smart. i merged down from a feature branch that we'd been deploying from, and updated ansible to pull from master. ran the deploy, and it treated that as "didn't change". i was *sure* it had just missed the branch change, but hopped on and looked, and sure enough, that clone is using master.
nicely done, ansible devs.
Reminder, the US congress is literally trying to exempt Transgender people from Civil Rights Protections.
https://www.themarysue.com/hr-2796-anti-trans-bill/
If you're in the USA and can, you really need to make some noise about this, it's lead by the Republicans as usual phone and/or write them. So yeah, get onto your congress representative now, I would but in Australia so I can only help spread the word
so the fixture teardown method was attempting to delete all the fixture data. only some of my tests had...already deleted the fixture data. and the teardown method gets unhappy when what it deletes doesn't match what it created.
for now this is all being applied to an in-memory sqlite db (yes, i know that leaves holes in my tests), so i'm just going to skip it for now. when i move off sqlite, i'll rewrite the offending tests so the fixtures can clean up after themselves.
am back in the timesink of fighting with my db fixtures library. the stuff i want it to do is apparently just complicated enough that it doesn't work all the time.
i'd used a workaround for a bunch of stuff originally, and just discovered i didn't technically need to. so now i'm scaling back what i'm using the workaround for, and trying to decide if it's worth fighting the errors popping up along the way.
i'd be gaining test readability, so i feel like it's worth _some_ time.
i don't think i knew what materials engineering was when i was in high school or college. but it's tops of the list of things i would want to try if i had a chance to redo my schooling and my career.
Wow. Photobucket just unceremoniously ended hotlinking for anyone who doesn't cough up $400 a year. Billions of images all across the web just became advertisements for Photobucket. This is unbelievable.
My login/password still work for now, so if you have an account and remember your credentials, I recommend backing up anything now. Who knows what'll happen next.
Everyone should also adblock Photobucket, especially if you frequent old forums, or you'll be seeing lots of these ads from now on.
i just typed "brew install exim", and i'm wondering exactly where i went wrong in my life that led me to this point.
it's always so satisfying to invest time in unit tests and watch them go off like fireworks when you make some deep plumbing changes.
not that i'm happy about having shit broken, including possibly testing assumptions, but seeing that they actually _fail_ when things are broken gives me the warm fuzzies.
i know it's advertising, but watching tom brady fail hilariously to move a rikishi while touring japan has made my morning. i couldn't not share it.
tried out a new test fixtures library for a new project at work. fills in sqlite tables for me based on my sqlalchemy setup, and also gets my plain-object access to the same data for verification. yay!
knocked out a bunch of simple tests, then went to try something that required (nominally supported) model relationships. oh, look a stack trace coming from the fixture setup call.
*goes to google some more*
*vows to tracer-bullet all needed functionality in new libraries next time*
4 more tries since then, all failed before getting to 2gb.
