Repository navigation
test/parallel/test-dgram-connect.js fails locally #27341
Copy link
Copy link
Closed
Labels
dgramIssues and PRs related to UDP and the dgram module.Issues and PRs related to UDP and the dgram module.good first issueIssues that are suitable for first-time contributors.Issues that are suitable for first-time contributors.testIssues and PRs related to Node.js core tests and test infrastructure.Issues and PRs related to Node.js core tests and test infrastructure.
Description
Activity
- addedtestIssues and PRs related to Node.js core tests and test infrastructure.Issues and PRs related to Node.js core tests and test infrastructure.dgramIssues and PRs related to UDP and the dgram module.Issues and PRs related to UDP and the dgram module.
on Apr 22, 2019 @Trott yeah, the issue is that the ISP may not be doing what it's supposed to do and it could e.g. hijack the invalid DNS request so that when you visit it in the browser it redirects you to a page full of their ads :/
- addedgood first issueIssues that are suitable for first-time contributors.Issues that are suitable for first-time contributors.
on May 2, 2019 I guess the easiest solution is to move this test to
test/internetbecause it sends out actual DNS requests.I guess the easiest solution is to move this test to test/internet because it sends out actual DNS requests.
I think this is fine, but I would just move that specific test not the whole file.
Reacted by Joyee Cheung and Rich Trott- added 2 commits that reference this issue
on May 13, 2019 - added 2 commits that reference this issue
on May 14, 2019
Metadata
Metadata
Assignees
Labels
dgramIssues and PRs related to UDP and the dgram module.Issues and PRs related to UDP and the dgram module.good first issueIssues that are suitable for first-time contributors.Issues that are suitable for first-time contributors.testIssues and PRs related to Node.js core tests and test infrastructure.Issues and PRs related to Node.js core tests and test infrastructure.
Does not reproduce if I turn my Wifi off (it's probably hijacking DNS requests to invalid domains), so I guess either this should be moved to internet instead, or we should mock the lookup.