Skip to content

fix: report longitude error in geohash assertion - #2361

Open
Nikolay Zdravkov (unsafePtr) wants to merge 1 commit into
microsoft:mainfrom
unsafePtr:fix/geohash-longitude-message
Open

Nikolay Zdravkov (unsafePtr) wants to merge 1 commit into
microsoft:mainfrom
unsafePtr:fix/geohash-longitude-message

Conversation

@unsafePtr

Copy link
Copy Markdown
Contributor

Report the longitude error in the longitude round-trip assertion message. It currently prints the latitude error, which gives the wrong diagnostic when the longitude check fails.

Copilot AI balanced review requested due to automatic review settings November 5, 2026 05:00

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

There are no active review issues with the change correcting the longitude assertion’s diagnostic error value.

No open issues 🎉

What changed in this PR

Corrects the longitude round-trip assertion diagnostic in the geohash tests so failures report the longitude error rather than the latitude error.

Changes:

  • Uses lonError in the failure message; assertion logic and numeric formatting remain unchanged.
File Description
test/​standalone/​Garnet.test.collections/​GeoHashTests.cs Reports the correct error value in the longitude assertion message.

Review effort: Balanced

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants