Skip to content
This repository was archived by the owner on Mar 10, 2020. It is now read-only.

fix: get correct remote node config #1120

Merged
merged 1 commit into from
Oct 4, 2019
Merged

Conversation

achingbrain
Copy link
Collaborator

I noticed some calls would fail during tests when the daemon was listening on non-standard ports, this was because when commands require other commands that use ky, we are passing the ky instance in as the sole property of an object that usually contains the host and port number of the remote node's API server.

I noticed some calls would fail during tests when the daemon was listening
on non-standard ports, this was because when commands `require` other
commands that use `ky`, we are passing the `ky` instance in as the
sole property of an object that usually contains the host and port
number of the remote node's API server.
@achingbrain achingbrain merged commit aca704b into master Oct 4, 2019
@achingbrain achingbrain deleted the pass-correct-config branch October 4, 2019 13:50
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants