Open Macil opened 4 years ago
I dunno what logger tool you're using, but if there's some way to capture the value of this
when this error pops up, that would probably be really helpful to tracking it down. Because you're activating a Property, it's possible there's something downstream from emitter
(whatever that happens to be) causing the issue.
I'm assuming you haven't been able to reproduce this yourself at all?
In a project that uses Kefir, I've seen a strange error show up yesterday in our client error logs. A single user hit this error a few dozen times in one session only. We haven't had anyone else ever hit this error, so it's pretty low priority for the project.
The stacktrace is very interesting to me. The error doesn't seem like something that should be possible. It implies that to-property.js's _onActivation method is being called on an object without an _emitValue method. Even if the application did something wrong like passing a non-stream to Kefir where a stream was expected, this seems like something that shouldn't be possible. But I don't understand the flow fully enough to be sure that this should be impossible. Maybe there's some kind of situation where it can happen if a property activates while a dependent stream is still being initialized.
Here's a simplified version of the application code where this is happening. The .onValue call at the bottom of the stack trace is the one here.
I checked that the project isn't doing something surprising like using different versions or instances of the Kefir library in a single project and then mixing streams from them.
(Kefir version 3.8.6)