Ask Bjørn Hansen 196f90a2b9 fix(db): use int for netspeed_active to prevent overflow ...

GetZoneStatsData and GetZoneStatsV2's netspeed_active values can
exceed 2 billion, causing 32-bit integer overflow. Changed from
int32/uint32 to int (64-bit on modern systems) to handle large
network speed totals.

- Update sqlc column overrides to use int type
- Fix type compatibility in dnsanswers.go zoneTotals map
- Regenerate database code with new types

Fixes https://community.ntppool.org/t/error-message-displayed-on-the-monitoring-score-page/4063

2025-09-21 00:08:21 -07:00

..

db.go

Update schema for monitors v4; use go tool

2025-06-21 03:49:02 -07:00

dbconn.go

db: less logging when opening a database connection

2025-01-06 19:33:45 +01:00

dynamic_connect.go

style: format Go code with gofumpt

2025-08-03 16:06:59 -07:00

models.go

fix(db): use int for netspeed_active to prevent overflow

2025-09-21 00:08:21 -07:00

monitor.go

Update schema for monitors v4; use go tool

2025-06-21 03:49:02 -07:00

otel.go

Update schema

2025-09-20 10:29:53 -07:00

querier.go

fix(api): protocol-aware monitor filtering for multi-protocol monitors

2025-07-27 00:37:49 -07:00

query.sql.go

fix(db): use int for netspeed_active to prevent overflow

2025-09-21 00:08:21 -07:00

server.go

Return not found for more recently deleted servers, too

2023-12-14 23:17:44 -08:00

tx.go

Add tracing

2023-10-14 04:01:43 -07:00

zone_stats.go

Use logger instance instead of default log/slog

2023-10-22 16:33:54 -07:00