Response time chart is empty

[arminus]

Describe the bug
The response time charts are empty for all of my monitors. Peekaping version v0.0.39

Database

• postgresql

To Reproduce
Happens for both existing and new monitors

Expected behavior
plot the response times

Screenshots

Desktop (please complete the following information):

• OS: Win20
• Browser Firefox
• Version 143.0.1

Additional context
No errors in the container log or the browser console

[arminus]

Switched from postgres to the sqlite-bundle image, issue is gone.

Maybe related; Lately, I've been observing issues with permissions on various (non-peekaping) images which use postgres, for some reason, they all do a kind of chmod to go-rwx, which often results in write errors. My current workaround is to set user: 1000:1000 for those postgres containers. But that doesn't work with the peekaping postgres bundle which then throws a permission error on some JS code during startup.

[brewle]

This should now be resolved by PR #260.

The issue only affects setups using PostgreSQL as the database backend.
Heartbeats were being recorded correctly, but the stats table remained empty, which resulted in:

• empty response time charts
• missing uptime percentages

The root cause was the UPDATE -> RowsAffected() -> INSERT pattern used in UpsertStat.
On PostgreSQL, RowsAffected() returns -1 for UPDATE statements without a RETURNING clause (lib/pq behavior). Because of this, the fallback INSERT was never executed, and the stats table stayed empty.

PR #260 replaces this logic with a single atomic:

INSERT ... ON CONFLICT (monitor_id, timestamp) DO UPDATE

This works correctly on both PostgreSQL and SQLite.

Please test with the build from #260 and let me know if the issue persists.

[HartD92]

@brewle fyi I had the same issue, tested with #260 which resolves the issue for me.