Skip to content
This repository was archived by the owner on Jun 18, 2026. It is now read-only.

fix: broaden friend edge detection to all resolved non-class locations - #137

Merged
sauravbhattacharya001 merged 1 commit into
masterfrom
fix/friend-edge-location-filter
Mar 30, 2026
Merged

sauravbhattacharya001 merged 1 commit into
masterfrom
fix/friend-edge-location-filter

Conversation

@sauravbhattacharya001

Copy link
Copy Markdown
Owner

Summary

The friend SQL query in Network.java was hardcoded to location = 'public', missing meetings at cafes, libraries, paths, and other resolved locations. This caused under-counting of friend edges.

Changes

  • Changed friend query filter from location = 'public' to location NOT IN ('class', 'unknown', '') to match the pattern used by stranger and familiar-stranger queries.

Fixes #134

The friend SQL query was hardcoded to location='public', missing meetings
at cafes, libraries, paths, and other resolved locations. This caused
under-counting of friend edges compared to stranger/familiar-stranger
queries which already used location NOT IN ('class','unknown','').

Align the friend query with the same inclusive filter used by the other
relationship types.

Fixes #134
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@github-actions github-actions Bot added database Database queries and schema size/xs labels Mar 29, 2026
@sauravbhattacharya001
sauravbhattacharya001 merged commit 15c5d90 into master Mar 30, 2026
4 of 8 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

database Database queries and schema size/xs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Friend edge detection limited to 'public' locations — misses other non-class locations

1 participant