Signals are lost in some cases
See original GitHub issueI’m not sure if this is a bug, but I found this strange behavior of signals getting lost on some cases.
const pool = kefir.pool();
const prop = pool.toProperty(() => 0);
const later = kefir.later(100, null);
const stream = later
.flatMapLatest(() => kefir.merge([prop.take(1), pool]))
.log('stream');
pool.plug(stream.take(1).map(() => 1));
I would expect stream to log with 0 and 1, but only 0 gets logged. Or I’m I misunderstanding this somehow?
To clarify issue a little bit, if I change .flatMapLatest(() => kefir.merge([prop.take(1), pool]))
to .flatMapLatest(() => prop)
it will log 0 and 1. So it seems pool won’t give signals in this case even though it should according to my understanding.
Issue Analytics
- State:
- Created 6 years ago
- Comments:10 (1 by maintainers)
Top Results From Across the Web
9 Reasons Why Cell Phone Signals Suddenly Go Bad
Find out the top 9 reasons why cell phone signals suddenly go bad and one definitive solution to fix them. Talk to the...
Read more >Why Do Cell Phone Signals Go Bad? What You Need To Know
Cell Phone signals often go bad when something is blocking its transmission from getting from the nearby tower to the phone itself. Sometimes ......
Read more >Can Cases Mess Up the iPhone's Signal?
Any given case may cause signal loss if the case design blocks the internal cell antenna. Most case materials, however, including leather or...
Read more >Interference with Radio, TV and Cordless Telephone Signals
Interference may prevent reception altogether, may cause only a temporary loss of a signal, or may affect the quality of the sound or...
Read more >Loss of signal detection and configurable gap-filling strategies
Because New Relic evaluates incoming data in specific windows of time, in many cases, the telemetry signals you send to New Relic can...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@tweinfeld Thank you! I didn’t know the order matters while merging streams. 🤔 Now when I know this I might be able to avoid issues like this. 👍
Sorry for bad description. What I wanted to say is that sometimes:
won’t work as you need and
y.merge(x.skip(1))
is a different thing. So your only option then may be a switch to statics:But it also boils down to order dependecy, yes.