jim/URLNotesGrabberCore
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: start replies fetch from newest, ignore stale DB timestamp

Browse Source 
The DB-derived MAX(N.timestamp)+1 for a post is unreliable - many notes
were stored with the same timestamp (likely crawl time, not the actual
note timestamp), so passing it as before_timestamp excluded all real
replies and returned an empty notes array. Diagnostics showed two
unrelated posts coming back with identical totals (1625/1021/603) and
zero notes.

Now we start with no before_timestamp (newest page) and let pagination
walk backward via each page's last-note timestamp.
This commit is contained in:
jim
2026-05-07 14:00:48 -05:00
parent 1da8a702ba
commit 1c7b6a1e86
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
URLNotesGrabberCORE/Program.cs
+2 -2
View File
@@ -452,11 +452,11 @@ namespace URLNotesGrabberCORE
const int MaxPages = 10; const int MaxPages = 10;
try try
{ {
Console.WriteLine($"[Reply Text] Fetching reply text for {blogName}/{postID}/{timestamp}"); Console.WriteLine($"[Reply Text] Fetching reply text for {blogName}/{postID}");
int replyCount = 0; int replyCount = 0;
int emptyReplyCount = 0; int emptyReplyCount = 0;
long pageTimestamp = timestamp; long pageTimestamp = 0;
int page = 0; int page = 0;
while (page < MaxPages) while (page < MaxPages)