Files
trading_bot_v4/docker-compose.telegram-bot.yml
mindesbunister 5d5868d802 critical: Fix Smart Validation Queue blockReason mismatch (Bug #84)
Root Cause: check-risk endpoint passes blockReason='SMART_VALIDATION_QUEUED'
but addSignal() only accepted 'QUALITY_SCORE_TOO_LOW' → signals blocked but never queued

Impact: Quality 85 LONG signal at 08:40:03 saved to database but never monitored
User missed validation opportunity when price moved favorably

Fix: Accept both blockReason variants in addSignal() validation check

Evidence:
- Database record cmj41pdqu0101pf07mith5s4c has blockReason='SMART_VALIDATION_QUEUED'
- No logs showing addSignal() execution (would log ' Smart validation queued')
- check-risk code line 451 passes 'SMART_VALIDATION_QUEUED'
- addSignal() line 76 rejected signals != 'QUALITY_SCORE_TOO_LOW'

Result: Quality 50-89 signals will now be properly queued for validation
2025-12-13 17:24:38 +01:00

34 lines
795 B
YAML

version: '3.3'
services:
telegram-trade-bot:
build:
context: .
dockerfile: Dockerfile.telegram-bot
container_name: telegram-trade-bot
restart: unless-stopped
env_file:
- .env.telegram-bot
dns:
- 9.9.9.9
- 8.8.8.8
- 8.8.4.4
environment:
- TELEGRAM_BOT_TOKEN=${TELEGRAM_BOT_TOKEN}
- N8N_WEBHOOK_URL=${N8N_WEBHOOK_URL}
- TELEGRAM_CHAT_ID=579304651
- TRADING_BOT_URL=${TRADING_BOT_URL:-http://trading-bot-v4:3000}
- API_SECRET_KEY=${API_SECRET_KEY}
healthcheck:
test: ["CMD", "python3", "-c", "import sys; sys.exit(0)"]
interval: 30s
timeout: 5s
retries: 3
start_period: 10s
networks:
- traderv4_trading-net
networks:
traderv4_trading-net:
external: true