This repository has been archived by the owner on Feb 12, 2024. It is now read-only.
Find testing strategy for tests that are using DNS #2899
Assignees
Labels
help wanted
Seeking public contribution on this issue
kind/enhancement
A net-new feature or improvement to an existing feature
kind/not-helia-issue
Comments
achingbrain
added
help wanted
|
js-ipfs is being deprecated in favor of Helia. You can #4336 and read the migration guide. Please feel to reopen with any comments by 2023-06-02. We will do a final pass on reopened issues afterwards (see #4336). This issue is most likely resolved in Helia, please try it out! related to #2000 ipfs/helia-ipns#53 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Multiple tests around in our ecosystem assumes there is a dns resolver that has a connection to the internet. The dependency on internet backbone is something we want to avoid in general, and also we want to make sure the tests are always working as expected.
One idea is to run a local dns server for the process where the tests are running, to use. Then we can setup whatever records we want, and resolve them via
.homefor example.Comes from ipfs-inactive/interface-js-ipfs-core#332 (comment)
The text was updated successfully, but these errors were encountered: