You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit e3214be
Browse filesBrowse the repository at this point in the historyBrowse files
fix(pipeline): set aside reports the old Worker misread as NANP
Reports stored before the bare-digit fix can't show whether "+1..." was
sent that way, so bare_digit_misreading judges them by two signs: the
number's +86 reading is already a known number, or its area code isn't
in service and no app sent it (no report id). It only judges reports
dated before BARE_DIGIT_FIX_DAY (2026-10-31 UTC, the day after the
Worker went out), so a spoofed caller ID in a dead area code reported
from then on is kept. The merge drops such reports at intake and sweeps
unpublished pending rows that already hold them; a row in the database,
an approved number, or a row whose events have all aged out is left
alone. The hot list skips the same reports.
The watch-list assertion block in test_report_pipeline is a new test;
no existing test was wrong. Its runner now sets
CALLSHIELD_BARE_DIGIT_FIX_DAY to the fixture's TODAY so the dated rule
holds whatever day the suite runs.
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -81,6 +81,7 @@ All notable changes to CallShield will be documented in this file.
81
81
- On a phone with two SIMs, the caller ID popup for a call on the second SIM closed the moment it opened. It went by the main SIM's call state, and that reads idle while the other SIM rings. The popup now watches each SIM and closes once every one of them is idle, the same way an outgoing call's warning does.
82
82
- On a phone with two SIMs, Answer and hang up now rejects a spam call when either SIM is roaming. Android doesn't tell call screening apps which SIM a call came in on, so CallShield only checked the main one, and a call on a roaming second SIM could get answered abroad, where answering can cost you.
83
83
- The report service now takes a number sent without a + only when it has ten digits, read as a US or Canadian number. Any other bare length is turned away, since nothing says which country it's from. A Chinese mobile sent as 15017944158 was being stored as +1 501-794-4158, a line in Arkansas, and could end up on the watch list. The import scripts for North American feeds still read a bare 1 plus ten digits as +1.
84
+
- The community report merge and the watch list now set aside reports from before that fix that were most likely misread that way. That's a +1 number whose +86 reading is already a known number, or one in an area code no phone line uses that didn't come from the app. A number already in the database or approved by hand is never set aside, and neither is a report from after the fix.
0 commit comments