Skip to content

testkit: Implements ForcedRoutingTableUpdate #796

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 22, 2021

Conversation

bigmontz
Copy link
Contributor

It also fix the GetRoutingTable request handler adding a default value where there is no routing table registered.

It also fix the GetRoutingTable request handler adding a default value where there is no routing table registered.
Copy link
Member

@robsdedude robsdedude left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔌

const provider = driver._getOrCreateConnectionProvider()

if (provider._freshRoutingTable) {
// Removing database from the routing table registry
Copy link
Member

@robsdedude robsdedude Oct 22, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll take the PR as is. But I'll suggest to extend that comment with a few words explaining why you decided to delete the RT and go through _freshRoutingTable instead of just calling _refreshRoutingTable which might seem like the better solution (but isn't as you commented).

@bigmontz bigmontz merged commit a29020d into 4.4 Oct 22, 2021
@bigmontz bigmontz deleted the 4.4-tk-add-ForceUpdateRouting-message branch October 22, 2021 16:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants