Repository navigation
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
The metadata response gives the MD5 of one database build. Requesting the download by date returns the latest build of that day, so a build published between the two requests causes a checksum mismatch. Request the download by the build_epoch from the metadata instead. The server always sends build_epoch, so the date request is gone. This ports maxmind/geoipupdate#566. Co-Authored-By: Claude Opus 5.5 <[email protected]>
3d25812 to
996f87a
Compare
pygeoipupdate now identifies the database to download by its build epoch rather than its date. The download request sends the
build_epochfrom the metadata response. A request by date returns the latest build of that day, so a new build published during an update could cause a checksum mismatch.The date request is gone. If the metadata has no
build_epoch, the update fails with aDownloadError. This needs STF-295 deployed first. Today production does not sendbuild_epoch.This ports maxmind/geoipupdate#566. That PR also fixes a response-body leak in the Go client. The Python client reads each response inside
async with, so it does not have that leak.🤖 Generated with Claude Code