Skip to content
New issue

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

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

Already on GitHub? # to your account

chore: update deps #1044

Closed
wants to merge 3 commits into from
Closed

chore: update deps #1044

wants to merge 3 commits into from

Conversation

guillaumemichel
Copy link
Contributor

@guillaumemichel guillaumemichel commented Feb 20, 2025

I am disabling QUIC for tests since some tests are randomly timing out in the CI (they are fine when run locally) when QUIC is enabled (some peers time out when connecting to each other). Everything was fine with quic-go v0.48.2 but something seems to have broken in quic-go v0.49.0 on which go-libp2p v0.40.0 depends.

IMO it is fine to disable QUIC from the DHT tests since the goal is to test the DHT behaviour and not the transports.

@libp2p/go-libp2p-maintainers @marten-seemann

@guillaumemichel guillaumemichel marked this pull request as ready for review February 20, 2025 16:44
@guillaumemichel guillaumemichel requested review from a team as code owners February 20, 2025 16:44
Copy link
Contributor

@MarcoPolo MarcoPolo left a comment

Choose a reason for hiding this comment

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

I'd like to understand why QUIC is causing flakiness here first. Let's investigate that first, then decide if we want to disable it (but I'd lean towards no without a compelling reason).

With QUIC we can mock a lot of the network in a better way than we can with the TCP transport. See this PR as an example of using a simulated connection to test holepunching: libp2p/go-libp2p#3044. Maybe that simulated connection code could be useful for debugging here?

@guillaumemichel
Copy link
Contributor Author

After deeper investigation, the problem seemed to be linked to the go version used by the CI. Fixed in #1048

@guillaumemichel guillaumemichel deleted the deps-20250220 branch February 21, 2025 12:42
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants