switch does not propagate cancel requests across switch boundary?
See original GitHub issueWhen switch
swaps the new stream with the old the cancel propagation terminates on a switch boundary, so if the inner stream was itself created through a switch
operator, the inner stream associated with the inner switch
is never canceled. This is different than the behavior in both Rx 4 and xstream.
most: http://www.webpackbin.com/4kP1_KOu- Rx 4: http://www.webpackbin.com/VyEKDF__W xstream: http://www.webpackbin.com/Ny5VwFdOZ
Isn’t this a bug?
Issue Analytics
- State:
- Created 7 years ago
- Comments:11 (4 by maintainers)
Top Results From Across the Web
Troubleshooting VLAN Trunk Protocol (VTP) - Cisco
This document provides information on how to troubleshoot VLAN Trunk Protocol (VTP).
Read more >Go Concurrency Patterns: Context
A Context carries a deadline, cancellation signal, and request-scoped values // across API boundaries. Its methods are safe for simultaneous ...
Read more >OpenFlow Switch Specification - Open Networking Foundation
THIS SPECIFICATION IS PROVIDED “AS IS” WITH NO WARRANTIES. WHATSOEVER, INCLUDING ANY WARRANTY OF MERCHANTABILITY,. NONINFRINGEMENT, FITNESS FOR ANY ...
Read more >Layer 2 Networking | Junos OS - Juniper Networks
Extension of Layer 2 VLANs across multiple switches using Spanning Tree ... the DHCP server propagation is not supported in Layer 2 transparent...
Read more >Chapter 1, Routing and Switching Strategies - O'Reilly
Not limited to routers, switches, and access points, these decisions are ... Two switches are interconnected via Port 3 on Switch 1 and...
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
@ntilwalli Thanks for all the additional info. I haven’t had a chance to dig into it, but it seems like there’s some sort of race condition related to the end of stream handling in switch. I should have time soon to look into it more.
@ntilwalli Your example seems potentially interesting. However, there are a couple things about it that make it harder to understand what is going on and whether there’s actually a problem. First, there’s just a lot going on in it, and second, it’s fairly different from either the rx or the xstream examples. Could you try to simplify it, i.e. try to find a more minimal example of the problem you think you’re seeing? I think that will help us figure out what’s going on. Thanks!