sxyazi/yazi · error

Receiver `{receiver}` does not have the ability to receive `

Error message

Receiver `{receiver}` does not have the ability to receive `{kind}` messages.

What it means

Targeted send validation in `ya pub`: a specific receiver Id was named and found among the peers, but that peer did not register the ability for this message `kind`. The faulting inputs are the receiver Id and the message kind.

Source

Thrown at yazi-cli/src/dds/shot.rs:72

		}
		Ok(())
	}

	pub(super) fn ensure_ability(peers: &HashMap<Id, Peer>, kind: &str, receiver: Id) -> Result<()> {
		match (receiver, peers.get(&receiver).map(|p| p.able(kind))) {
			// Send to all receivers
			(Id::ZERO, _) if peers.is_empty() => {
				bail!("No receiver found. Check if any receivers are running.")
			}
			(Id::ZERO, _) if peers.values().all(|p| !p.able(kind)) => {
				bail!("No receiver has the ability to receive `{kind}` messages.")
			}
			(Id::ZERO, _) => Ok(()),

			// Send to a specific receiver
			(_, Some(true)) => Ok(()),
			(_, Some(false)) => {
				bail!("Receiver `{receiver}` does not have the ability to receive `{kind}` messages.")
			}
			(_, None) => bail!("Receiver `{receiver}` not found. Check if the receiver is running."),
		}
	}
}

View on GitHub (pinned to 5f901b886b)

Solutions

  1. Pick a receiver that advertises the ability for this message kind (check via `ya pub --list`).
  2. Register the ability in the target receiver's plugin before publishing to it.
  3. Verify the receiver Id is current — restart receivers if versions changed.
Defensive patterns

Strategy: validation

When it happens

Trigger: Thrown at yazi-cli/src/dds/shot.rs:72 when the library encounters an invalid state.

Common situations: See trigger scenarios.


AI-assisted analysis of sxyazi/yazi@5f901b886b (2026-09-02). Data as JSON: /api/errors/4308d4cec3daba36. Report an issue: GitHub.