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

Описание и применение

Ошибка в парсинге десятичного значения cpu_hours в панели управления привела к потере данных о тарифах и продлении. Исправление было внесено в 1.3.0 версии, восстановив корректную работу.

Задача

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

Результат

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

Рабочий процесс

• 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

Доказательства

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

Источник

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

Источник

The fix shipped 46 minutes after the pull request opened.

Источник