Gary Casey
Gary Casey
That's just plain weird.
It's related to our overall testing approach, particularly automated retesting when deiendencues change and yes we need to discuss it
Moving to PR43
Colin - yes caching of the secondary info from root lookup is something we should do. Cache invalidation trigger could be if the client fails to (re)connect to the secondary...
Good question. findSecondary's responsibility is simply to look up the secondary's address from the root server, so I'd say we should leave that responsibility as is, and have the caching...
I'm going to remove myself as a reviewer on this PR. I'd like to see all of the apps tested against this branch
@sarika01 @murali-shris @cconstab @XavierChanth How much of a problem has this been? Is it still important enough to keep open in the backlog at least?
We'll be getting to this over time. Target for PR29 is > 25%. Once we hit that we'll set target > 40% and so on
less important than continuing to enhance functional and end-to-end test coverage
@cconstab as a partial mitigation workaround we could have the sender start (before sync) by sharing something (anything) with the other atSign, then waiting for sync.