[wp-meta] [Making WordPress.org] #5117: WP dashboard city locations (encoding?) wrong

[Making WordPress.org]

#5117: WP dashboard city locations (encoding?) wrong
-----------------------------+---------------------
 Reporter:  ramon fincken    |       Owner:  (none)
     Type:  defect           |      Status:  new
 Priority:  normal           |   Milestone:
Component:  Events API       |  Resolution:
 Keywords:  has-screenshots  |
-----------------------------+---------------------
Changes (by dd32):

 * keywords:  has-screenshots needs-patch => has-screenshots
 * milestone:  Q2 =>


Comment:

 > I'm not 100% sure on this, but I think this happens because the table
 has the latin1_general_ci collation set for it. Think the table needs a
 restructure to be fully utf8mb4 for all rows and the collation.

 The table collation is set to latin1 (as all of WordPress.org should be)
 but the data is utf8 and treated as such since the connection to the table
 should be utf8 (When using not-the-events-api to query it, that needs to
 be set manually)

 It looks like this is a MySQL ordering issue, adding an exact-match in the
 ordering seems to result in the correct row being returned, I suspect this
 wasn't picked up at the time of building since the row orderings on disk
 in the table have since changed, previously the first result would've been
 the correct, but now the correct row is a few results in.

 Commit incoming, the Caches on location lookups is 12hours, so if everyone
 could recheck the API responses after that time, it'd be appreciated to
 check that everything is still responding as intended. That goes for more
 than just Zurich/Amsterdam, "normal" things that were previously correct
 should also be checked. Keep in mind that the WordPress Timezone and
 Locale are also taken into account, so even if it was working fine for
 someone, double check it.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5117#comment:5>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org