Skip to content

DirectCommand: multiaddr not working #1288

@alexcos20

Description

@alexcos20

When issueing directCommands, you should be able to specify multiaddr if you want to deal with another node and that node address is not in peerStore/DHT.

Now it fails with 500

Image

PS: if you pass multiaddr as array, it works:

{
    "command":"jobs",
    "jobId":"abb5b55ad429c57dd2e2f73541b233b972a5c2c1f5c5ca99fff0bb200d67aafd",
    "node":"16Uiu2HAm94yL3Sjem2piKmGkiHCdJyTn3F3aWueZTXKT38ekjuzr",
    "multiAddrs":["/ip4/157.66.255.31/tcp/9000"]
}

so we just need to make sure that we validate the request and give a nice error message

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type: BugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions