Anton Gilgur

> Monthly release cadence is about the max "every 2 weeks" was if we go with the "release manager" approach I mentioned [above](https://github.com/argoproj/argo-workflows/issues/12592#issuecomment-2064373530) who's just on backporting duty for a...

While I have the context, and given the priority & impact of this, I'm just going to go ahead and make the changes requested above myself and push them to...

> I'm also going to build a test image and push to a test registry for folks to try and test out Pushed [`agilgur5/argo-workflow-controller:fix-configmap-informer`](https://hub.docker.com/layers/agilgur5/argo-workflow-controller/fix-configmap-informer/images/sha256-48c229a153ff18c9ab6fc94b4f62340e6155a6d68c25937c4ce733f73b444345?context=repo) for testing

It's still very necessary, although the upstream issue may have been resolved in k8s 1.30 if our [hypotheses](https://github.com/argoproj/argo-workflows/issues/11657#issuecomment-2050434984) are correct, but even if that is accurate it may break again...

That's one option. I intentionally did not list a specific dep as there's a few different components available that should be compared/evaluated

Closing this as superseded by Garett's #13100

@andreineculau thanks a ton for the links! I'm using [`facebook-atom/jest-electron-runner`](https://github.com/facebook-atom/jest-electron-runner/), not this library, but running `xvfb` [solved the hanging issues](https://github.com/agilgur5/physijs-webpack/pull/15#issuecomment-558864963) I was having! For anyone looking for example code, can...

Re-read this since #10 was created which duplicates this, and I didn't seem to specify how to workaround this as I did downstream. Per https://github.com/agilgur5/react-signature-canvas/issues/22#issuecomment-420914077, you can use a `background-color`...

I don't believe there's a workaround for this as the `CanvasContext` manipulation is not user-facing. That's why I wrote that this may require new props to support. It is an...

It's not an error, it's a warning, so by definition you can ignore it. And the warning is about a newer browser feature that did not exist until years after...