Spaces:
Running
Running
Commit History
8 days ago
-
resolved bugs r
060643f
-
multiple changes added
831da15
-
shift mysql to neondb
ab8ae7f
-
fix: scope IPv4-force to MySQL only; surface real discovery errors
The IPv4 monkeypatch (added for the Hostinger IPv6-routing issue) was applying process-wide regardless of which DB backend was active. With DATABASE_URL now on the SQLite fallback, it was doing nothing useful while still forcing every other outbound call (Groq, OpenAI, Hunter, SignalHire, ddgs) onto IPv4-only -- which can route an anycast/CDN API through a worse path than IPv6 would pick. Now gated on settings.sqlalchemy_url actually being mysql+pymysql. Also: a Groq discovery run just failed with 'Connection error.', which tells you nothing. _describe_exception() walks __cause__/__context__ so the job result carries the real underlying error next time. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>cab8436 -
fix: SQLite fallback for remote MySQL, unreachable from HF Spaces
Hostinger's shared-hosting firewall silently drops connections from cloud/datacenter IP ranges (confirmed: same host:port succeeds from a residential IP, times out -- never refused -- from every cloud origin tried). Remote MySQL is unreachable from this Space until that is resolved on Hostinger's side. database.py now branches on the DATABASE_URL scheme: the MySQL path is completely unchanged, sqlite gets its own pool/connect_args (no pool_size/max_overflow, check_same_thread=False, PRAGMA foreign_keys=ON so ON DELETE CASCADE actually fires) and auto-creates its parent directory. Temporary and explicitly ephemeral -- the file does not survive a container restart. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>bdcfad2 -
update database.py
bb0a8a7 -
initial commit
ff3c2e9