zellij-org/zellij · error
Invalid MouseEventType: {}
Error message
Invalid MouseEventType: {} What it means
Error "Invalid MouseEventType: {}" thrown in zellij-org/zellij.
Source
Thrown at zellij-utils/src/ipc/protobuf_conversion.rs:4605
{
type Error = anyhow::Error;
fn try_from(
event: crate::client_server_contract::client_server_contract::MouseEvent,
) -> Result<Self> {
use crate::client_server_contract::client_server_contract::MouseEventType as ProtoMouseEventType;
let event_type = match event.event_type {
x if x == ProtoMouseEventType::Press as i32 => {
crate::input::mouse::MouseEventType::Press
},
x if x == ProtoMouseEventType::Release as i32 => {
crate::input::mouse::MouseEventType::Release
},
x if x == ProtoMouseEventType::Motion as i32 => {
crate::input::mouse::MouseEventType::Motion
},
_ => return Err(anyhow!("Invalid MouseEventType: {}", event.event_type)),
};
let position = event
.position
.ok_or_else(|| anyhow!("MouseEvent missing position"))?
.try_into()?;
Ok(crate::input::mouse::MouseEvent {
event_type,
left: event.left,
right: event.right,
middle: event.middle,
wheel_up: event.wheel_up,
wheel_down: event.wheel_down,
wheel_left: event.wheel_left,
wheel_right: event.wheel_right,
shift: event.shift,
alt: event.alt,View on GitHub (pinned to e839bfffa5)
Solutions
- Validate the value against the allowed enum range before constructing the message.
- Ensure client and server use matching protobuf definitions; regenerate bindings if versions differ.
When it happens
Trigger: Occurs when a protobuf enum value received over IPC has no matching variant; conversion rejects the unknown value.
Common situations: Typical of version skew between client and server, or a malformed/corrupted IPC message.
AI-assisted analysis of zellij-org/zellij@e839bfffa5 (2026-08-19).
Data as JSON: /api/errors/93f5fed378c6c3fa.
Report an issue: GitHub.