IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
solved this wrong by isolating it first at http level, however now at
the ipfs::unixfs::cat level the http implementation is looking small as
it should be.
touched some error types and converted them to thiserror.
perhaps the error message requirements have changed, since this worked
right away? aah nope, they must concern other uses of walk_path. well,
this passes the tests either way.
for example, we might want to just do the splitting manually over a
String. this can be added back, but right now it allowed removal of
unnecessary dependencies at tests.
320: Implement Ipfs::find_peer and /dht/findpeer r=koivunej a=ljedrz
Builds on https://github.com/rs-ipfs/rust-ipfs/pull/319, only the last 2 commits are new.
Introduces `Ipfs::find_peer` and `/dht/findpeer` that return addresses belonging to the given `PeerId`; if they are connected to already, the values are returned right away, otherwise the local DHT records are checked.
Blocked by https://github.com/rs-ipfs/rust-ipfs/pull/319.
Co-authored-by: ljedrz <ljedrz@gmail.com>
315: Use explicit Multiaddr wrappers r=koivunej a=ljedrz
Whether a `Multiaddr` contains `Protocol::P2p` (i.e. essentially `/p2p/PeerId`) or not has a lot of bearing on conformance tests, the internal object and APIs and error-handling. Since it is easy to introduce related human errors, it would be a good idea to enforce some type safety here by introducing 2 wrapper objects: `MultiaddrWoPeerId` and `MultiaddrWithPeerId`.
The extent to which they should be applied (in lieu of `Multiaddr`) is a matter for discussion - in my initial attempt I decided to apply them quite liberally, as it results in more type safety (there are still a few plain `Multiaddr`s left though).
Co-authored-by: ljedrz <ljedrz@gmail.com>
110: add: p2p suffixes to multiaddrs from identify r=koivunej a=koivunej
not verified but indirectly used by the conformance tests when dialing a peer with an expected peerid.
Not 100% sure if this should be done, at least long as #105 is done at least to accept the multiaddrs with `/p2p/`.
Co-authored-by: Joonas Koivunen <joonas@equilibrium.co>
Co-authored-by: ljedrz <ljedrz@gmail.com>
