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

[DNM] Debug 1631 #1917

Closed
wants to merge 38 commits into from
Closed

[DNM] Debug 1631 #1917

wants to merge 38 commits into from

Conversation

altonen
Copy link
Contributor

@altonen altonen commented Oct 17, 2023

βœ„ -----------------------------------------------------------------------------

Thank you for your Pull Request! πŸ™ Please make sure it follows the contribution guidelines outlined in
this document and fill
out the sections below. Once you're ready to submit your PR for review, please
delete this section and leave only the text under the "Description" heading.

Description

Please include a summary of the changes and the related issue. Please also include relevant motivation and context,
including:

  • What does this PR do?
  • Why are these changes needed?
  • How were these changes implemented and what do they affect?

Use Github semantic
linking

to address any open issues this PR relates to or closes.

Fixes # (issue number, if applicable)

Closes # (issue number, if applicable)

Checklist

  • My PR includes a detailed description as outlined in the "Description" section above
  • My PR follows the labeling requirements of this project (at minimum one label for T
    required)
  • I have made corresponding changes to the documentation (if applicable)
  • I have added tests that prove my fix is effective or that my feature works (if applicable)

You can remove the "Checklist" section once all have been checked. Thank you for your contribution!

βœ„ -----------------------------------------------------------------------------

altonen and others added 14 commits September 19, 2023 10:35
Co-authored-by: Anton <anton.kalyaev@gmail.com>
Recent optimization in `V1Lazy` caused syncing to stall if if a request
was sent to a peer who didn't support the request-response protocol.
Addresses getting removed from Kademlia for completely innocuous reasons
such as keep-alive timeouts are causing the node to have a lot of dial
failures. The dial failures happen because when `ProtocolController`
tries to connect to a node, and when the address is trying to be fetched
from from `Discovery`, it returns an empty vector since `Kademlia` no
longer holds any addresses for the peer.
Co-authored-by: Dmitry Markin <dmitry@markin.tech>
@altonen altonen requested a review from athei as a code owner October 17, 2023 14:54
@altonen altonen requested a review from a team October 17, 2023 14:54
@altonen altonen requested a review from koute as a code owner October 17, 2023 14:54
@chevdor
Copy link
Contributor

chevdor commented Oct 19, 2023

A fix to the PRDOc issue is ready in #1947

@paritytech-cicd-pr
Copy link

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable-int
Logs: https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/4158836

@paritytech-cicd-pr
Copy link

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable 1/3
Logs: https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/4158817

@paritytech-review-bot paritytech-review-bot bot requested a review from a team November 1, 2023 11:43
@seadanda seadanda removed the request for review from a team March 14, 2024 09:04
@bkchr bkchr closed this Jul 17, 2024
@bkchr bkchr deleted the altonen-debug-1631 branch July 17, 2024 12:36
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.

4 participants