Root of the problem is there are two code paths that result in the banner addition code getting called. One of which is an error state, but it's a state that just indicates an image comparison failed. This is fine.

I did some refactoring to make it easier to debug/fix and pushed the commits to my WIP detangle-node-sh branch. I think I have a better sense for what's happening now. Working on fix...

Looking...

GH action for auto generation of CHANGELOG.md on version tag push
https://github.com/wikimedia/pixel/pull/267

I'm digesting pixel.js to better understand how to refactor it to make maintenance and adding new extensions / configs easier

I'm working on adding auto-changelog

Add changelog to help with versioning
https://github.com/wikimedia/pixel/pull/258

Using the new-ish --progress=plain flag in docker compose and docker build solved this:

Closing for now. May add more notes as further changes are made which could further reduce disk usage.

More aggressively remove Docker artifacts on clean
https://github.com/wikimedia/pixel/pull/259

Update .nvmrc to Node 18
https://github.com/wikimedia/pixel/pull/262

Edit: Disregard. I need to look into this more. I think I don't have a handle on exactly when things get kicked off...

Watching the docker folder's size change live as it runs with this:

I'm also looking at if it might be safe to add a call to docker system prune -af to either the cron script or the pixel clean func...

I have this PR as well which losslessly optimizes PNG as they are created:

It was pointed out to me that the server had my Node 18 branch checked out instead of main (iirc I didn't do it!)

I think I fixed one of the issues related to this today

I suppose an alternative (more simple?) approach would be to modify lipsum to add descriptions 🤔

This patch seems to work creating an empty description exception for the lipsum tool:

I got my vue setup spun up and a rough first pass at the first screen converted to a vue single file component:

Ok it's live in groups 1 and 2 and still seems ok ( with the exception of the icon toggle state issue previously identified )

@NHillard-WMF I'm unsure if I should move this out of QA? Description says "QA To be done as part of T343920", so probably 🤷‍♂️

Triple-checked it on a couple group 1 and 2 production wikis

^ @bwang ( i hear jon's off for a bit )

I see this says it's scoped to only backend code. Is there anything I can do to help kick the UI / functionality tires?

Will do!

Status:❓Need More Info
Environment: beta
OS: macOS Ventura
Browser: Safari 16.6, Chrome 115
Device: MBP

lgtm 👍

Sure!

Status:❓Need More Info
Environment: beta
OS: macOS Ventura
Browser: Safari 16.6, Chrome 115
Device: MBP