Ambiguity in /memory text format

Open
#127 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
go
Domain
networking

Research direction

Start by reading the /memory multiaddr text-format handling and the linked pull request #92. Reproduce serialization and parsing when the payload contains /, then determine whether the ambiguity is resolved; done means /memory payloads serialize and parse without ambiguity, or the proposed change is reverted.

Written by the indexing model from the issue text.

Description

The /memory multiaddr can contain an arbitrary payload. But if this payload contains a /, then you can't properly serialize it without introducing an ambiguity.

I would propose to revert https://github.com/multiformats/multiaddr/pull/92

Dominant language
Go
Stars
482
Forks
87
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from multiformats/multiaddr

All issues in multiformats/multiaddr

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.