fix: resolve 8 integration test compilation errors (#46)
CI / CI (push) Successful in 11m36s

## Problem
8 integration test files failed to compile due to:
1. Ambiguous float types (Rust 2024+ stricter inference)
2. chrono 0.4 API change (`with_hour` removed)
3. Missing `sqlx` + `base64` in `[dev-dependencies]`
4. `<` parsed as generics instead of comparison
5. Incorrect assertion (3^5=243 > 100)

## Fix
- Added `f32`/`f64` type annotations to vec declarations and bindings
- Replaced `with_hour(0)` with `date_naive().and_hms_opt(0,0,0).unwrap().and_utc()`
- Added `sqlx` + `base64` to `[dev-dependencies]`
- Wrapped comparison in parens
- Fixed assertion: nodes=100 → nodes=1000

## Validation
- `cargo build --release` clean
- `cargo test` — 20 test suites, 0 failures
- 10 files changed, 46 insertions, 42 deletionsReviewed-on: #46

Co-authored-by: rock <[email protected]>
This commit was merged in pull request #46.
This commit is contained in:
2026-09-09 01:22:33 +00:00
committed by rock
parent 1e5c3d1433
commit b15072e12d
33 changed files with 140 additions and 2541 deletions
+28
View File
@@ -0,0 +1,28 @@
{
"results": [
{
"id": "chunk-abc123",
"level": "L1",
"score": 0.95,
"text": "Kubernetes uses port 8080 for API server",
"source": "transcript://session-001"
},
{
"id": "chunk-def456",
"level": "L2",
"score": 0.87,
"text": "Common debugging pattern for CrashLoopBackOff pods",
"source": "transcript://session-002"
},
{
"id": "chunk-ghi789",
"level": "R",
"score": 0.72,
"text": "See kubectl troubleshooting guide section 3.2",
"source": "obsidian://poimen-vault/kubectl.md"
}
],
"total_hits": 127,
"search_time_ms": 145,
"query": "fix kubernetes port conflict"
}
+33
View File
@@ -0,0 +1,33 @@
# Kubernetes Troubleshooting Guide
## Port Conflicts
When a port conflict occurs on port 8080, check for existing services:
```bash
kubectl get svc --all-namespaces | grep 8080
```
### Common Causes
1. Multiple services binding to same NodePort
2. Host network pods conflicting with node services
3. Ingress controller port overlap
## CrashLoopBackOff
Pods enter CrashLoopBackOff when the container exits repeatedly.
### Diagnosis Steps
1. Check pod logs: `kubectl logs <pod> --previous`
2. Check events: `kubectl describe pod <pod>`
3. Check resource limits: memory/CPU constraints
4. Check liveness probes: incorrect health check paths
### Resolution
- Increase memory limits if OOMKilled
- Fix application startup errors
- Adjust probe timing (initialDelaySeconds)
- Check environment variable configuration
+16
View File
@@ -0,0 +1,16 @@
2025-01-15T10:00:00Z INFO Starting service on port 8080
2025-01-15T10:00:01Z DEBUG Database connection pool initialized (max=20)
2025-01-15T10:00:02Z INFO Health check endpoint ready at /health
2025-01-15T10:00:05Z WARN High memory usage detected: 85% of 512Mi limit
2025-01-15T10:00:10Z ERROR Connection refused: temporal-frontend:7233
2025-01-15T10:00:15Z INFO Retry attempt 1/3 for temporal connection
2025-01-15T10:00:20Z INFO Connected to temporal-frontend.temporal.svc.cluster.local:7233
2025-01-15T10:00:25Z DEBUG Worker registered on task queue: poimen-taskqueue
2025-01-15T10:00:30Z INFO Processing ingest request: project=poimen source=transcript://session-001
2025-01-15T10:00:31Z DEBUG Entity extraction complete: 5 entities found
2025-01-15T10:00:32Z DEBUG Fact extraction complete: 3 facts found
2025-01-15T10:00:33Z INFO Contradiction check: 0 contradictions detected
2025-01-15T10:00:34Z INFO Ingest complete: chunk-abc123 (145ms)
2025-01-15T10:00:40Z WARN Slow query detected: 850ms for hybrid search
2025-01-15T10:00:45Z ERROR Pod OOMKilled: poimen-worker-abc123 (memory limit exceeded)
2025-01-15T10:00:50Z INFO Pod restarted: poimen-worker-abc123 (restart count: 1)