TestGeoIPMatcher6US fails with v2ray-geoip >= 202508050201

[felixonmars]

What version of V2Ray are you using?

5.37.0/5.38.0

What's your scenario of using V2Ray?

Packaging for a Linux distribution.

What problems have you encountered?

The test suite fails at TestGeoIPMatcher6US:

=== RUN   TestGeoIPMatcher6US
    condition_geoip_test.go:194: expect US geoip contain 2001:4860:4860::8888, but actually not
--- FAIL: TestGeoIPMatcher6US (0.21s)

Downgrading v2ray-geoip to 202507050144 fixes it.

[AkinoKaede]

2001:4860:4860::8888 is now matched by CA. I think it is because MaxMind staff thinks CA stands for California.

[Loyalsoldier]

Actually, the v2fly/geoip repository now uses the free DB-IP GeoIP database as the default, starting from commit 9b440f0 as noted in issue #108.

I believe 2001:4860:4860::8888 being matched to CA is a mistake by DB-IP. Let’s wait for next month’s DB-IP GeoIP database release to see if it’s fixed.

[xiaokangwang]

In theory, we can rewrite the test to use another address for testing, or pin the geoip file as a test vector. If Maxmind don't fix it, I will.