Bruce Conrad

This may be just a restatement (though with less detail) of issue #567

Related to issue #549, which fixing this issue would also fix.

Playing with this candidate rule: ``` rule addKeyValue { select when wrangler new_key_value_pair Id re#(.+)# key re#(.+)# value re#(.*)# setting(Id,key,value) pre { buses = established() bad_key = ["Id","Rx_role","Tx_role","Rx","Tx","Tx_host"] >< key...

Have had success with this rule, testing in `localhost:3000`: ``` rule saveKeyValuePair { select when wrangler new_key_value_pair key re#(.+)# value re#(.*)# setting(key,value) pre { bus = findBus(established()) invalid = bus.isnull()...

Rather than modifying the `io.picolabs.subscription` ruleset, I think it is nearly as easy to have your ruleset "wrap" it and use the relationship `Id` to map to the desired auxiliary...

For this to work, every rule in Wrangler needs to pass through all of the event attributes that it receives, as it cannot know about correlation identifiers that might be...

There are some cases where an event is sent rather than raised. In particular, where we are crossing over from the child's perspective to the parent's and vice versa. For...

Note: just changed the three "event" links in the previous comment to permalinks.

This issue impacts [another repo](https://github.com/Picolab/fully-sharded-database/commit/ecc63223a3a16c1be772e3eeedc25c7bcf26de93).

So far, a very small change has satisfied one of that kind of path, in [this commit](https://github.com/b1conrad/KRL-experiments/commit/e1cd46f9eedf6ccc1a1adc04214b62a30f994e8b) of KRL-experiments.