Roland Hummel

Yeah I've played around with different event types etc. **But** the general issue is that the Scale components seem to detach their internal state from the values that are given...

It's this one: ```js // Project Euler Second Value for Condition Check test('if the number is greater or equal to 2167', () => { expect(problem44(2167)).toBe(8476206790) }) ``` I **guess** it's...

I just realized this is even more severe as assumed initially: Since we're running the test in a pre-commit hook, the simple act of **just committing changes locally** becomes a...

However, having this long-running tests clogs up everyone's workflow and not "just" the CI, therefore I recommend to **not** just uncommenting the test but rather explicitly skipping it. This way,...

Yup! 👍 I mereley mentioned the issue no. in the commit message but didn't _close_ it.

Jest has an `onlyChanged` option that I've set up in the pre-commit hook. If that's what you like, we could also switch to that behavior for the CI, as well.

@raklaptudirm I've updated the CI config, as well 👍

I guess I could set that up with GitHub Actions, yeah. But as long as #1193 is not solved, the `master` build will take forever to complete.

I've updated the Workflow accordingly - please take a look 😀

This issue should be closed now, right? I just `npm install`ed on a M1 machine without any issues :)