Andrew Pikul

Yes this is still in progress! Some newer releases are out and official releases are just making their way through the pipeline. It's mainly fixing up documentation and integrating with...

Kaleido does not `require` a specific version of chrom/ium, but since kaleido relies on chrom/ium, and since occasionally google let's bugs slip through into version bands (say, bug starts in...

I wouldn't install with the package manager, I would install with our CLI tool since its the last known good version. If I have access I can debug this tomorrow,...

Alright, I'm in this now. I have to: - [ ] Modify workflow files for consistency (slim builds can be tough) - [ ] Enable verbose logging in GHA -...

im going to add an environmental variable or check for one that circle ci/gha set. Chromium is very noisy! We use pytest, which captures all logging output and dumps it...

I'm about to send a fix today for error #1, but I still have to increase verbosity of debugging to decide whats going on in error #2

50% done @stefanv, will push some new versions of dependencies today. Should be able to resolve it this week, its close to first on the list.

I think we commented at about the same time. Running tests now to see if fix 1 works. Then debugging coming in for fix 2 this week, probably tomorrow, maybe...

Looks all green, but I'm still suspicious that there may need to be some reliability engineering. I'll build in better debugging to be ready for that.

It seems that all I had to do with expand type support in choreographer's json serializer. The other error went away and I don't know how to reproduce it, but...