Max Ammann

Not really, there were no events which could have caused that. Im also unsure whether this is a problem or not. The warning/message has been added recently to kernels (2021)....

Ill reopen if i discover it again.

Hm reopen? That the kernel can log these messages is quite new. So I haven't found a hint whether this is informational or actually bad.

In that case we should probably heap allocate the state. Can you think of an example which allows reproduction? Maybe we can will the state artificially.

Hitting the same issue, I suppose this is hardcoded somewhere

This would be very cool!

There is a similar feature actualyl! https://github.com/jfairbank/redux-saga-test-plan/blob/master/docs/integration-testing/partial-matching.md Works for my purposes.

Having a similar case with jest mocking. not sure yet why they dont match

The reason for this is that redux-saga-test-plan probably checks for identify (===) when comparing the fn and arguments in a CALL effect comparision. Now, jest is a bit crazy when...

It would be cool if the serializer could show that the arguments serialize to the same string but have a different identity.