* feat: webhooks * feat: Enhance webhook security and typing, fix validation and encryption bugs * fix: lint / types * fix: rm files * fix: rm mcp * fix: pydantic issue with TypedDict in python version <= 3.11 * fix: pre-commit hook for test coverage * fix: simplify API -- store url on workspace * fix: redo architecture * fix: webhook body * fix: make workspace optional * fix: comments * refactor: add webhook secret * fix: CR comments * feat: use deriver for webhooks * use key-value approach * feat: add work unit key to deriver * fix: add work unit key to webhooks * fix: tests * fix: cr comments #2 * fix: endpoint structure; make webhook delivery into a function; add tests; other general comments * chore: change webhook secret, fix test event and workspace_id, use async with * feat: implement queue.empty and backfill * fix: unique constraint * refactor: queue to use outerjoin and remove skip locked; also fix publish queue.empty * fix: tests * fix: migration - make columns non-nullable |
||
|---|---|---|
| .. | ||
| tests | ||
| README.md | ||
| harness.py | ||
| run_tests.py | ||
README.md
Honcho Development Harness
This directory contains a development harness script that makes it easy to run Honcho locally with a Docker database.
Overview
The harness.py script orchestrates the complete Honcho development environment:
- Database Setup: Starts a PostgreSQL database in Docker with a configurable port
- Database Provisioning: Runs Alembic migrations to set up the database schema
- Configuration: Uses environment variables to configure Honcho's database connection
- Service Startup: Starts both the FastAPI server and deriver process
- Configuration Verification: Prints the actual configuration that Honcho is using
- Monitoring: Provides real-time logs from all services
- Cleanup: Gracefully shuts down all services when stopped
Prerequisites
- Python 3.8+
- Docker and Docker Compose
- Honcho project dependencies installed (
uv sync)
Usage
Basic Usage
Run the harness with default settings (database on port 5433):
python tests/bench/harness.py
Custom Database Port
Run with a custom database port:
python tests/bench/harness.py --port 5434
Custom Project Root
If running from a different directory:
python tests/bench/harness.py --project-root /path/to/honcho
Command Line Options
--port: Port for the PostgreSQL database (default: 5433)--project-root: Path to the Honcho project root (default: current directory)
What Gets Started
When you run the harness, it will start:
- PostgreSQL Database: Running in Docker on the specified port
- FastAPI Server: Available at http://localhost:8000
- API Documentation: Available at http://localhost:8000/docs
- Deriver Process: Background worker for processing messages
Configuration
The harness uses environment variables to configure Honcho's database connection:
DB_CONNECTION_URI: Set topostgresql+psycopg://testuser:testpwd@localhost:{port}/honcho
The script will print the actual configuration that Honcho is using after the FastAPI server starts. This gives you complete visibility into how Honcho's configuration system resolved the settings from environment variables, config files, and defaults.
Stopping the Services
Press Ctrl+C to gracefully stop all services. The harness will:
- Stop the FastAPI server and deriver processes
- Stop the Docker database container
- Clean up temporary files (Docker Compose configuration)
Troubleshooting
Database Connection Issues
If the database fails to start or connect:
- Check if port 5433 (or your custom port) is already in use
- Ensure Docker is running
- Try a different port:
--port 5434
Configuration Issues
The script will print the actual configuration being used. If you see unexpected values:
- Check if you have a
config.tomlfile that might be overriding environment variables - Verify that the environment variables are being set correctly
- Check the Honcho configuration documentation for precedence rules
Integration with CI/CD
This harness can be used in CI/CD pipelines for integration testing. The script will:
- Use temporary directories for isolation
- Clean up all resources on exit
- Provide clear error messages for debugging
- Exit with appropriate status codes
- Use environment variables for configuration (no file conflicts)
Test Runner
The run_tests.py script executes JSON-formatted tests against a running Honcho instance. The harness must be running.
Running Tests
-
Start Honcho using the harness:
python tests/bench/harness.py -
In another terminal, run the tests:
# Run all tests python tests/bench/run_tests.py # Run a specific test # Test judge uses claude 3.5 sonnet python tests/bench/run_tests.py --test 1.json
Test Workflow
For each test, the runner:
- Creates a workspace for the test
- Adds all messages from the JSON to sessions
- Waits for deriver queue to be empty
- Executes queries as
.chat()calls - Judges responses using expected_response field
Test JSON Format
Tests are defined in JSON files with this structure:
{
"sessions": {
"session1": {
"messages": [
{
"peer": "alice",
"content": "Hello, how are you?"
},
{
"peer": "bob",
"content": "I'm good, thank you!"
}
]
}
},
"queries": [
{
"query": "How is Bob doing?",
"expected_response": "Good",
"session": "session1", // optional
"peer": "alice" // optional
}
]
}
Command Line Options
--tests-dir: Directory containing JSON test files (default: tests/bench/tests)--test: Run a specific test file--honcho-url: URL of running Honcho instance (default: http://localhost:8000)--anthropic-api-key: Anthropic API key for response judging, uses LLM_ANTHROPIC_API_KEY if not given--timeout: Timeout for deriver queue to empty (default: 60 seconds)