Skip to content

Critical: Broken installation, missing dependencies, and non-functional core logic (Is this project valid?) #9

@f13end

Description

@f13end

I have spent the last few hours trying to get this project running on a macOS environment (Python 3.11), following the documentation step-by-step. The experience suggests that the codebase is largely untested and possibly AI-hallucinated, as it lacks fundamental dependencies and functional logic.

Here is a summary of the critical issues I encountered:

  1. Broken "Quick Start" & Missing Files
    The documentation suggests running pip install wifi-densepose and then cp example.env .env.

Issue: The example.env file is NOT included in the pip package distribution.

Fix: I had to clone the repo manually to find the configuration template.

  1. Missing Dependencies
    Even after setting up a clean virtual environment, the requirements.txt or setup process is incomplete.

Error: ModuleNotFoundError: No module named 'greenlet' (Required for SQLAlchemy async).

Error: ModuleNotFoundError: No module named 'aiosqlite' (Required for the default DB fallback).

Error: ModuleNotFoundError: No module named 'websockets' (Required for the client script example).

Fix: I had to manually install these packages one by one.

  1. Configuration & Pydantic Crashes
    The configuration loading logic is broken.

Error: pydantic_core._pydantic_core.ValidationError: 1 validation error for Settings allowed_origins Extra inputs are not permitted.

The .env file logic clashes with Pydantic's strict validation. I had to manually edit/delete lines in .env just to get the server to boot.

  1. Authentication Loop (401 Unauthorized)
    Despite setting ENABLE_AUTHENTICATION=false in .env, the server persists in returning 401 Unauthorized for stream endpoints.

I had to forcefully inject environment variables (ENABLE_AUTHENTICATION=false wifi-densepose start) and kill lingering processes to bypass this. The configuration file seems to be ignored in certain contexts.

  1. The "Mock" Reality
    After fixing all the above and finally connecting to the WebSocket stream, I realized the system is merely running in MOCK_HARDWARE mode, outputting random/generated coordinates.

I dug into the source code to find the actual CSI (Channel State Information) processing logic for Intel/Atheros cards, but the core implementation seems generic or missing.

Conclusion: Is there a working branch of this project that actually interfaces with WiFi hardware? Currently, this repository appears to be a "vibe-coded" boilerplate with high-level architecture but no low-level implementation, riddled with basic dependency errors.

Environment:

OS: macOS (Silicon)

Python: 3.11

Install Method: pip & source

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions