The bug a well-reviewed repo can't show you

Description and use

A decimal cpu_hours value from the Pulsed Media API caused JSON parsing errors in the pmss-fleet-manager dashboard, blanking billing data. The issue was fixed by changing the struct to *float64 in release 1.3.0.

Problem

A dashboard tool misinterpreted a decimal CPU hours value from an API, causing billing and renewal data to be blanked for affected services.

Outcome

The bug was fixed within 46 minutes of the pull request opening, restoring correct billing and renewal data for affected services.

Workflow

• Read the dashboard source and API feed
• Identify mismatch between API decimal and dashboard int64 model
• Create test fixture with 3.4 and null
• Modify struct to use *float64
• Add tests for new parsing logic
• Merge changes via pull request
• Release v1.3.0
• Verify functionality in production

Evidence

Go's encoding/json will not put 3.4 into an int64; it returns an error.

Source

The fix in release 1.3.0 is small: CPUHours *float64 json:"cpu_hours"

Source

The fix shipped 46 minutes after the pull request opened.

Source