Anthony Martinez @ajmartinez@librem.one

Any week that starts with an LDAP crash is not going to go well.

I’ve never really felt like getting a car in NL until today’s pile of train delays had me zigzagging all over creation and turned a 2hr trip into 4....

I’d rather a motorcycle though if it came to that.

@Gina looks lekker AF

@kyle nice!

@kyle ain’t seen one of those in a long time

@purism just placed my Librem 5 order! Looking forward to real convergence. Not needing to carry a laptop on my cycle commute is going to be great.

@Gina similar issues for me regardless of browser or platform.

Crazy week at work ended on a positive note. After making an insane number of commits and PRs across way too many projects it finally became clear where the blocking issue was hiding. With that fixed progress can continue. The lack of meaningful tests at any level, from the unit up through systems integration, is a serious problem.

@dos nice!

Taking a break from a gazillion screen hours to make something with my hands. #handspun #yarn

@pbx I should take a look at the cost of the two resources in that app service plan. One is a “native” Function App, and the other is backed by a container image I developed. The latter is served out of a container registry I also pay for so the Function App is probably cheaper. I’ll take a look tomorrow.

Today I deployed an Azure Function App in #python. When it was all said and done, and my machine sullied by MS libraries, I was left wondering how this was any different than any other container I could have deployed behind an app service. The logs showed me the answer: there is no technical difference. Also, the container MS selected is significantly less performant than the one I rolled for a different service. I may just rewrite the thing tomorrow.

I really should do TDD more often. Or I feel like it is helpful for me. Particularly now with something like seven active (semi-related) projects. It’s pretty rough when use of one from the other reveals a bug that has impacts on four different projects. I was able to fix one such case today without impacting the public API but it was less than fun.

#tdd #dev #foss

@stevenroose and yes for the fpm case I’d use it with the same form as done in the docs here: https://fpm.readthedocs.io/en/latest/source/dir.html

Just ship your binary, any applicable config defaults, docs, and your license. You can declare system dependencies as well, and should if they exist. Help options on fpm are a little better than the docs these days to be honest.

@friend @stevenroose yeah, native-tls will pull in openssl-sys as a dependency for Linux triples. This will not cause problems if your target is the same distro (and version) as your build machine. If it’s not all bets are off. For my specific case this left two options: enable the optional feature of including a vendored OpenSSL in my binary, or move to rustls. Either results in static linking of TLS libs in my project.

#Rust

Need to write some tests for a system I’ve developed for $dayJob. I hit some unexpected corners today. They were easy enough to resolve, but they never should have happened in the first place.

@stevenroose check out fpm for making packages. Pretty easy to use.

@schrieveslaach cross is exactly what I used for the 62s run on my laptop. cross dropped support for openssl, with good reasons discussed in an issue on their repo. Using their image as a base and adding openssl is trivial, however the resulting binaries only work on all targets if you use the ‘vendored’ feature to include a static openssl. It was overall less hassle to change my project to use rustls. Thanks for the response!