get_social reputation graph is always empty: 440 transfers parsed, giver column unrecognised #227

New issue

Closed

opened 2026-08-12 23:14:25 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-12 23:14:25 +00:00

Member

QA sweep, Eco via Sirens, day 40, 2026-08-12.

Observed

get_social returns:

"perTypeCounts": {"Play": 6295, "FirstLogin": 124, "ReputationTransfer": 440},
"totalReputationTransfers": 440,
"reputationEdges": [],
"topReputationGivers": [],
"topReputationReceivers": [],
"warnings": ["ReputationTransfer: 440 transfer(s) parsed but the giver column was not recognized (tried Citizen, Giver, GiverCitizen, FromCitizen, Sender, Player)"]

The tool's headline feature — "a reputation graph showing who reps whom" — produces nothing on a server with 440 reputation transfers.

Credit where due

This is the best-behaved failure in the whole tool surface: it says exactly what it tried and why it gave up, instead of silently returning []. Filing it as a functional gap, not a reporting one.

Next step

Needs the actual column name from a live ReputationTransfer export row. Worth logging one unrecognised row's keys (at debug level) so the candidate list can be extended without a round trip.

Also

Play: 6295 day-by-day series shows day 39 at 259 against a declining trend (day 38 = 28, day 40 = 104). Not necessarily wrong, but odd enough to be worth a glance while in here.

QA sweep, Eco via Sirens, day 40, 2026-08-12. ## Observed `get_social` returns: ```json "perTypeCounts": {"Play": 6295, "FirstLogin": 124, "ReputationTransfer": 440}, "totalReputationTransfers": 440, "reputationEdges": [], "topReputationGivers": [], "topReputationReceivers": [], "warnings": ["ReputationTransfer: 440 transfer(s) parsed but the giver column was not recognized (tried Citizen, Giver, GiverCitizen, FromCitizen, Sender, Player)"] ``` The tool's headline feature — "a reputation graph showing who reps whom" — produces nothing on a server with 440 reputation transfers. ## Credit where due This is the best-behaved failure in the whole tool surface: it says exactly what it tried and why it gave up, instead of silently returning `[]`. Filing it as a functional gap, not a reporting one. ## Next step Needs the actual column name from a live `ReputationTransfer` export row. Worth logging one unrecognised row's keys (at debug level) so the candidate list can be extended without a round trip. ## Also `Play: 6295` day-by-day series shows day 39 at 259 against a declining trend (day 38 = 28, day 40 = 104). Not necessarily wrong, but odd enough to be worth a glance while in here.

coilyco-ops referenced this issue

2026-08-12 23:34:54 +00:00

Tracking: 2026-08-12 full-surface QA sweep of the eco MCP (22 tools, 23 findings) #240

coilyco-ops referenced this issue

2026-08-12 23:36:09 +00:00

Tracking: 2026-08-12 full-surface QA sweep of the eco MCP (22 tools, 23 findings) #240

coilyco-ops referenced this issue

2026-08-12 23:47:23 +00:00

Tracking: 2026-08-12 full-surface QA sweep of the eco MCP (22 tools, 23 findings) #240

coilyco-ops referenced this issue from a commit

2026-08-13 06:02:36 +00:00

fix(social): name the columns the reputation export actually carries