#dailystandup — Public Fediverse posts

Yesterday I sat through the 2nd day of that agentic conf then I built a game on Unity when I got home last night; the first tutorial for the editor features

Today I'd do one call with a fellow dev assessing a PoC; then later will look at things we need for https://webtoo.ls -- big move next week

#DailyStandup

Kollege: "Zuerst konnte ich mich ein paar Stunden nicht einloggen, danach wollte ich mich nicht einloggen..."

#FeelYouBro
#Office
#HomeOffice
#DailyStandUp

Me when I can’t remember a single thing I did yesterday #scrum #agile #dailystandup

Scrum Process - Designed for planning to ensure the software project stays on course. Monitored through sprints and daily standups with the team and product owner. #scrum #sprint #dailystandup #productowner #scrummaster

I haven't posted a #DailyStandup since last Wednesday b/c posting is emotional labor and I've been emotionally used-up by shocking revelations in my personal life.

But! I have been working!

Been doing:
- On Saturday I went to a Colorado Green Builders' Guild event—getting #FreeSoftware onto HVAC equipment! #OpenHVAC
- Inventing a test-harness for Single Board Computers that I've been fantasizing about for years (thread/)

Will do:
- Tomorrow I'm going to the Northern Colorado Climate Meetup

#DailyStandup

- I think I've completed the terrible preprocessor hack that I'm calling `fuse_optdoc.h`
- Working on auditing libfuse's documentation.
- Helping @amerl set up a server

#DailyStandup

Since Friday:
- The nspawn FUSE PR got merged! https://github.com/systemd/systemd/pull/34067

Today:
- Re-auditing libfuse to make sure that all end-user-facing options are documented. Involves some fancy wrangling of the C preprocessor. The preprocessor hackery felt like a good self-contained puzzle to solve to start the week.

#DailyStandup Yesterday:
- Got the #systemd nspawn FUSE PR to pass CI (…but it's failing again now‽)
- Benchmark #ruby json patches https://github.com/flori/json/pull/567#issuecomment-2333350013 …"interesting" change in baseline variance since April

Today:
- Respond to feedback on the nspawn PR
- Feel spent, figure unstructured work will turn into something productive.… not so far

Other:
- Bugs on https://www.lukeshu.com/imworkingon/ 😞

#DailyStandup Woops, didn't post Tuesday or yesterday. But it's been productive!

- #Parabola's #Ruby is updated!
- Submitted a Fix to #ArchLinux's Ruby https://gitlab.archlinux.org/archlinux/packaging/packages/ruby/-/merge_requests/7
- Made a nice README for Parabola's GPL-compatible Ruby releases https://github.com/parabola-gnulinuxlibre/ruby-json
- Got to "lgtm" on adding FUSE support to #systemd nspawn https://github.com/systemd/systemd/pull/34067

Today:
- Getting the nspawn FUSE PR's CI to pass
- Updating+benchmarking the GPL-fix to upstream ruby-json.

#DailyStandup

So I'm working on upgrading #Parabola's #Ruby. But the ARM build takes forever and so my iteration time on solving problems is slow.

In the course of this I've found some bugs in #Qemu https://fosstodon.org/@lukeshu/113069912188713315 I'm working around them by disabling affected tests if we're running in a qemu chroot. After I get the bew Ruby out, I'll look into fixing the Qemu bugs... but IDK how I'm going to prioritize that against other existing work.

#DailyStandup

What I did yesterday:
- Responded to feedback on the nspawn FUSE PR https://github.com/systemd/systemd/pull/34067
- Looked at upgrading #Parabola Ruby 3.0→3.2. Filed https://gitlab.archlinux.org/archlinux/packaging/packages/ruby/-/merge_requests/6

What I'm doing today:
- Upgrading Parabola's Ruby.
- Looking into CI failures on the nspawn FUSE PR.

#DailyStandup

What I did yesterday:
- Got a new version of the systemd-nspawn FUSE PR pushed off

What I'm doing today:
- Responding to feedback on said PR.
- you decide!

#DailyStandup

What I did yesterday:
- I was trying to get a new version of the nspawn-fuse PR ready
- but I went down some yaks with the #systemd tests, ending up with some hacking on #mkosi.

What I'm doing today:
- A little more work on mkosi. I want better reporting of its capabilities based on what's installed; no more "error, do you have createrepo_c installed?" 20min into a build. I want a real #Parabola story for mkosi.
- Anyway, I'm too many yaks deep, I should get back to nspawn-fuse.

No real #DailyStandup yesterday or today because of dealing with family stuff.

But I did put up https://github.com/mailprocessing/mailprocessing/pull/16 yesterday morning.

#DailyStandup

- On Friday I decided to work on #Parabola stuff to take a break from the doc parser.
- But then some hardware came and I worked on reverse-engineering my Sensi Predict to patch their firmware to hopefully keep them out of landfills. #OpenHVAC
- But then yak lead to another and now I'm working on supporting FUSE inside of nspawn containers. #systemd https://github.com/systemd/systemd/issues/17607

#DailyStandup

Yesterday:
- Made a minor change to the glib doc PR based on feedback; it is now landed #gtk https://gitlab.gnome.org/GNOME/glib/-/merge_requests/4187
- Kept working on getting the gi-docgen parser to pass its tests

Today:
- Still working on the gi-docgen parser. Current status is only 57 failing tests (out of almost 2 million).
- There are some emails I should do. We'll see if I actually do.

#DailyStandup

- Inching ever closer to my gi-docgen parser tests passing
- I found some mistakes in the glib2 docs' conversion from gtk-doc to gi-docgen, putting together an MR to fix those upstream. #gtk (edit: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/4187)

#DailyStandup

So close to being happy with the new gi-docgen parser.

The 71 failures in pymdext.FuzzFencedCodeXHTML are the core HTML-BlockProcessor and the pymdext FencedCode-BlockProcessor clashing with eachother. I know what's wrong, but am trying to figure out a way to fix it that isn't a PITA.

The 4300 failures in gidocgen.FuzzHTML are that plus issues with GI-DocGen syntax extensions. It looks like most of them are the test harness not handling [type@name] links correctly.

#gtk

#DailyStandup

Got back from #FOSSY last night (instead of mid-day, because ✨airlines✨).

Gotta email/follow up with several folks who I exchanged business cards with. #OpenHVAC.

Still working on the new gi-docgen parser. #gtk

#DailyStandup Whoops, no post yesterday

What I did yesterday:
- Fixed more discrepancies between the new doc-parser and existing gi-docgen #gtk
- Reworked the test-util library to be more coherent

What I'm doing today:
- Reworking the tests to use persistent Python processes when testing against gi-docgen (and gtk-doc); this seems to improve the run-time for my expanded >100k entry test corpus from 2h45m to 3m

What I'm doing tomorrow:
- Getting on an airplane and flying to Portland for #FOSSY

#DailyStandup

Today:
- Updated some out-of-date #Parabola packages
- Picked up the Parabola stickers to give out at #FOSSY. Very happy with how they turned out.
- Still trying to iron out discrepancies in the new gi-docgen-compatible doc-parser. #gtk

#DailyStandup

I've fixed a number of places where the new doc-parser disagrees with gi-docgen. Hoping to have all of the core markdown disagreements resolved today, and move on to the bits of extension syntax tomorrow. It looks like all of the remaining disagreements in the core markdown might actually be problems in the tests' normalization steps, not actual problems with the parser. #gtk

#DailyStandup

Yesterday:
- Fixed some O(n²) space and time issues in the new doc-parser's inline-parser. #gtk

Today:
- Discovered this morning that the #Parabola build server's sshd wasn't responding. A system update had bungled our SSO config. Fixed that.
- I think I've got the new doc-parser's block parser behavior up to matching Python-Markdown 3.6 (it was matching 3.4.4 before).

Next up:
- Fixing the inline parser. I suspect all of the diffs come down to 1 big bug and 1 small bug.

Second meeting of the week postponed. But they are both moved to same day next week.

#dev #dailyStandup