Skip to content
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

feat(portalnet): add rfn lookup to gossip #1267

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

njgheorghita
Copy link
Collaborator

What was wrong?

How was it fixed?

To-Do

Comment on lines -63 to -67
if all_nodes.is_empty() {
// If there are no nodes whatsoever in the routing table the gossip cannot proceed.
warn!("No nodes in routing table, gossip cannot proceed.");
return 0;
}
Copy link
Member

Choose a reason for hiding this comment

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

Shouldn't this still be here?

@KolbyML
Copy link
Member

KolbyML commented Apr 24, 2024

I think the same result would have happened if you ran master on your home node running latest. So I think both cases should have been tested as a control.

Debugging and fixing why we are having provider issues is the highest issue then this. I do think this is a smarter way of gossipping.

But I think "solving"

  • get receipts returning null
  • the timeout thing you told me about are higher priority
    because as you mentioned in call if the 3 bridges were running it doesn't matter if 1 bridge can seed the whole network.

Without the logs or seeing if there was provider errors I don't think I can comment anything of value on the results you told me of the tested you reported to me earlier today

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.

None yet

2 participants