Subscriptions And Registration Not Being Forwarded Over RLink On Reconnect Or Late Join about crossbar HOT 1 OPEN

first of all, kudos for diving that deep into rlinks and router-to-router operations;)

the code for rlinks, including the features that it depends on (such as the meta API) is pretty complex. there will be bugs. however, it is - I would say - quite organized, and in fact, the problems you described are likely in the file you mentioned

https://github.com/crossbario/crossbar/blob/master/crossbar/worker/rlink.py

I'm currently busy with other things and hence didn't look deeply into what you raised and mention, however, from my point of view, one general comment:

The bugs still there are related to complex situations including recovery of node failures in a network of nodes and such, and reliably fixing them without introducing new bugs will require automated tests.

Poking around in the code without automated test cases will unlikely succeed (because of the complexity).

My overarching, general main worry hence is: how do we come up with a suitable set of test scenarios and automated tests to cover router-to-router app messaging ... to test the promises r2r makes wrt apps?

from crossbar.