Frontmatter
| id | 9046 |
| title | Fix: DevRank Tracker Timestamp Update Logic |
| state | Closed |
| labels | bugai |
| assignees | tobiu |
| createdAt | Feb 7, 2026, 11:16 PM |
| updatedAt | Feb 7, 2026, 11:18 PM |
| githubUrl | https://github.com/neomjs/neo/issues/9046 |
| author | tobiu |
| commentsCount | 1 |
| parentIssue | 8930 |
| subIssues | [] |
| subIssuesCompleted | 0 |
| subIssuesTotal | 0 |
| blockedBy | [] |
| blocking | [] |
| closedAt | Feb 7, 2026, 11:18 PM |
Fix: DevRank Tracker Timestamp Update Logic
tobiu added parent issue #8930 on Feb 7, 2026, 11:17 PM
tobiu assigned to @tobiu on Feb 7, 2026, 11:17 PM

tobiu
Feb 7, 2026, 11:18 PM
Input from Gemini 3 Pro:
✦ Fixed the
updateTrackerlogic bug that prevented updates for users withnulltimestamps.Fix
- Changed the condition
existingTime === undefinedtoexistingTime == null(which covers bothnullandundefined).- This ensures that users with
lastUpdate: null(new candidates) are now correctly updated with the new timestamp instead of being skipped.Code
} else if (existingTime == null || (update.lastUpdate && update.lastUpdate > existingTime)) {Code committed to
devbranch.
tobiu closed this issue on Feb 7, 2026, 11:18 PM
Fix a logic bug in
Storage.updateTrackerwherenulltimestamps prevent updates.The Bug: The current comparison logic
(update.lastUpdate && update.lastUpdate > existingTime)fails whenexistingTimeisnull. In JavaScript, comparing a string tonull(e.g.,'2026-01-01' > null) evaluates tofalse.Consequence: Users with
lastUpdate: null(newly discovered users) never get their timestamp updated after a successful scan. They remainnullintracker.jsonand are re-scanned indefinitely by the Updater.Fix: Update the condition in
apps/devrank/services/Storage.mjsto explicitly treatnullas an update-able state.if (existingTime == null || (update.lastUpdate && update.lastUpdate > existingTime))(using
== nullcovers bothnullandundefined)