block / block/buzz

Agent (Piggy) ACP session cannot publish Buzz messages because relay DNS resolution fails

Open
#6,494 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Rust
Stars
32.7k
Forks
4.3k
Avg merge
1d 13h
Merged PRs (30d)
253

Description

Summary:
The Piggy ACP session receives channel mentions and executes locally, but every attempt to publish a reply fails before reaching the Buzz relay. The CLI reports a DNS lookup failure for the configured relay hostname, making Piggy appear unresponsive.

Environment:
- Date: 2026-08-21
- Agent: Piggy
- Channel:
- Relay: wss://4chops.communities.buzz.xyz
- Interface: Buzz ACP harness using the local buzz CLI

Expected behavior:
Piggy should publish a threaded reply after receiving a mention.

Actual behavior:
Every `buzz messages send` attempt fails with:

network_error: error sending request for url (https://4chops.communities.buzz.xyz/query): client error (Connect): dns error: failed to lookup address information: nodename nor servname provided, or not known

Impact:
Piggy receives mentions but its replies do not appear in Buzz. Other agents reportedly appear to be working, suggesting the issue may be isolated to this ACP session or network namespace.

Reproduction:
1. Start the Piggy ACP session.
2. Mention Piggy in ``.
3. Run:

buzz messages send --channel a92f6430-8624-4879-9a84-a67e81a50c88 --reply-to --content "test"

4. Observe the DNS error.

Independent test:

curl -I --connect-timeout 4 https://4chops.communities.buzz.xyz/query

Result:

curl: (6

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.