dropUntil doesn't complete output when other completes
See original GitHub issueDocs of dropUntil
actually stand that:
Starts emitting the input stream when another stream emits a next event. The output stream will complete if/when the other stream completes.
But actually, it is not the case, due to this output
stream just start to emit when other
stream completes.
Test for this case actually tests that output
starts when other
complets, though it is called should complete the stream when another stream emits complete
.
So there’s is something wrong with either the operator’s code or its docs/tests.
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
java - Showing process completed but no output is coming up
I am trying to create a program that accepts two numbers and outputs the smallest digit in one number that is larger than...
Read more >Operators
Chaining Operators. Most operators operate on an Observable and return an Observable. This allows you to apply these operators one after the other,...
Read more >Apache Kafka's Exactly-Once Semantics Are Now Easier & ...
This results in throughput drop until the rebalance is complete. ... Another fatal error occurs when the producer cannot assign sequence ...
Read more >Why Crunch Mode Doesn't Work: Six Lessons [2005]
Or output can turn negative as stupefied employees commit catastrophic errors that destroy previously completed work or capital.
Read more >xstream | Yarn - Package Manager
endWhen(other). Uses another stream to determine when to complete the current stream. When the given other stream emits an event or completes, the...
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
So this actually should nor start emitting source (which is a current actual behavior) nor should complete it (which is a behaviour described in docs and test). 😃
Hey @whitecolor, let me know if behavior in my PR makes sense to you - I’m happy to clarify here how it is changed.