feat(scrapers): enable cian_city_sweep (proxy alive, sweep is cookieless) #1568
No reviewers
Labels
No labels
admin
analytics
auth
automation
bug
business
chore
ci
compliance
data
data-moat
docs
duplicate
dx
enhancement
Fable 5 ревью
feedback/max
generative
GG-форсайт
needs-discussion
needs-human
observability
pause-bots
performance
priority/p0
priority/p1
priority/p2
priority/p3
scope/backend
scope/db
scope/devops
scope/frontend
scope/qa
scrapers
security
site-finder
stage/1
stage/2
status/blocked
status/done
status/needs-analysis
status/needs-fix
status/qa
status/ready
status/review
status/wip
tech-debt
tradein
ux
week ревью 1
wontfix
вторичка
ИРД
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lekss361/gendesign#1568
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "feat/enable-cian-city-sweep"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Migration
118_enable_cian_city_sweep.sqlre-enables the dormantcian_city_sweepschedule to restore novostroyki + vtorichka cian listing coverage.Why it was off, and why it's safe to enable now
cian_city_sweepwas seededenabled=false(107) on a stale "proxy dead" assumption from 2026-05-31 (last attempt aborted on anchor timeouts). As a result cian's ~15k active rows became a frozen late-May snapshot — only ~28 of 15067 re-seen within 14 days, and the 9659 active novostroyki never refreshed.Verified on prod 2026-06-16:
status:OK, fresh IPs). The "proxy dead" premise is stale.CianScraperself-warms its curl_cffi (chrome120) session via a homepage GET;cian_detail.fetch_detailopens its ownAsyncSession(chrome120 +cian_proxy_url). Neither uses the DBcian_session_cookies. Only the separatecian_history_backfill(source-provided priceChanges) needs those cookies — they're stale since 05-31, tracked separately for human re-upload.Prod smoke proof (controlled, via
scrape_schedulesnext_run=now)lots_fetched=560, lots_inserted=89, lots_updated=471, 0 errors.detail_enriched=3/3, houses_enriched=4, 0 detail failures.Both completed
done. After verification, prod was set to the production config this migration encodes; the migration makes the enable reproducible (a fresh DB rebuild would otherwise re-apply 107's disabled seed).Config
enabled=true, nightly 02:00-05:00 UTC (separate proxy egress from avito — no contention), paramspages_per_anchor=3, detail_top_n=10, enrich_houses=true, request_delay_sec=5, radius_m=1500.next_run_atbootstrapped to tomorrow 02:30 UTC.Test plan
cian_city_sweepenabled; first nightly run refreshes cianlast_seen_atRefs #759