# dap: Support IPv6 addresses in TCP transport \(\#52244\) · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/5aa7eaa508e043a5f68ffec16af09b2ce6da8404)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: 5aa7eaa508e043a5f68ffec16af09b2ce6da8404

Requested commit: 5aa7eaa508e043a5f68ffec16af09b2ce6da8404

Commit: 5aa7eaa508e043a5f68ffec16af09b2ce6da8404

Tree: 0d062e2649e29476c962b291378278be98fd33a8

Author: moktamd

Committer: GitHub

## Message

```
dap: Support IPv6 addresses in TCP transport (#52244)

The DAP TCP transport layer was hardcoded to `Ipv4Addr`, so IPv6
addresses like `fd00::a` in a debug config's `connect.host` always
failed with `hostname must be IPv4: invalid IPv4 address syntax`.

Replaced `Ipv4Addr` with `IpAddr` and `SocketAddrV4` with `SocketAddr`
across the `task`, `dap`, `dap_adapters`, and `project` crates. The WASM
extension API still uses `u32` for the host field to avoid a breaking
WIT interface change; IPv4 round-trips through extensions as before.

Fixes #52237

Release Notes:

- Fixed DAP TCP transport rejecting IPv6 addresses when connecting to
remote debug adapters.

---------

Co-authored-by: moktamd <moktamd@users.noreply.github.com>
```

## Parents

- [d7d1b5404499fce236989d42dbe5db7a8ed3c8fa](https://git.cafe/gitcafe/zed/commit/d7d1b5404499fce236989d42dbe5db7a8ed3c8fa?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/5aa7eaa508e043a5f68ffec16af09b2ce6da8404?format=markdown)