Skip to content

MQTT and Redis Streams dispatch are non-functional stubs (vendored no-op hiredis/mosquitto) #32

Description

@DonPrus

The MQTT and Redis Streams transports look implemented but perform no network I/O — every call silently succeeds against fake vendored libraries:

  • deps/hiredis/hiredis.c (34 lines) — redisConnect returns a context with fd = -1 and never dials; redisCommand fabricates a REDIS_REPLY_STATUS reply so "callers see success" (its own comment).
  • deps/mosquitto/mosquitto.c (56 lines) — mosquitto_connect, mosquitto_publish, mosquitto_subscribe, mosquitto_loop_forever all immediately return MOSQ_ERR_SUCCESS; no sockets, no broker.
  • src/redis_client.zig:58-61 and src/mqtt_client.zig:69-72 — the "listener" threads just sleep(100ms) in a loop until shutdown; no message is ever received or dispatched.

Net effect: configuring the Redis Streams or MQTT dispatch appears to work (logs, clean startup, successful publishes) but nothing is ever sent or received, which is worse than an explicit failure.

Suggested fix: either implement the transports against the real hiredis/mosquitto, or (short term) fail config validation / log a prominent warning marking these backends experimental and non-functional, and note it in the README.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions