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

p2p/enode: implement per-source timeout in FairMix #25962

Merged
merged 5 commits into from
Nov 8, 2022

Conversation

zhiqiangxu
Copy link
Contributor

No description provided.

@fjl
Copy link
Contributor

fjl commented Oct 10, 2022

Good catch! Instead of deleting this field, we should really investigate why it isn't used.

@zhiqiangxu
Copy link
Contributor Author

zhiqiangxu commented Oct 10, 2022

Good catch! Instead of deleting this field, we should really investigate why it isn't used.

Seems it's unused since 1st day?

@fjl
Copy link
Contributor

fjl commented Oct 10, 2022

I think what I wanted to do there is, use this source-specific timeout for exponential backoff when one source gets stuck. The part that's missing is actually applying the source specific timeout instead of m.timeout.

@zhiqiangxu
Copy link
Contributor Author

I think what I wanted to do there is, use this source-specific timeout for exponential backoff when one source gets stuck. The part that's missing is actually applying the source specific timeout instead of m.timeout.

OK, added that missing part back.

@fjl fjl changed the title p2p/enode: mixSource.timeout is unused p2p/enode: implement per-source timeout in FairMix Nov 7, 2022
@fjl fjl merged commit 4cb1fca into ethereum:master Nov 8, 2022
@fjl fjl added this to the 1.11.0 milestone Nov 8, 2022
shekhirin pushed a commit to shekhirin/go-ethereum that referenced this pull request Jun 6, 2023
nibty pushed a commit to FairCrypto/go-ethereum that referenced this pull request Apr 10, 2024
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