Starting earlier today, the 'popularity' fields are now a mixture of floats and strings while they used to be floats.
For example, if you look at this output: https://api.themoviedb.org/3/movie/10611?api_key=123&language=en-US&append_to_response=similar
I see both this: popularity 2.548249 and popularity "2.3815020000000002"
I see it with everything (Movies, TV and all request types) that have the popularity field as output. Go(lang) is giving me headaches handling that properly. I don't mind if it's either float or string but a mixture is problematic.
Also... I remember that the popularity field could have values like 1234.56 but is it now changed to 1...10?
Thanks!
Non podes atopar unha película ou serie? Inicia sesión para creala.
Queres valorar ou engadir o elemento a unha listaxe?
Non es membro?
Resposta de Travis Bell
no 27 de xuño do 2018 ás 11:31AM
I've discovered what is causing this and the fix will be going out shortly. You'll have to wait the usual ~8 hours for the cached items to expire before you see it fixed everywhere.
Nothing has changed here, it's still 0..infinity.
Thanks!
Resposta de Jendrik Bertram
no 28 de xuño do 2018 ás 10:10AM
The problem still persists and it happens to all numeric fields. Should the fix already be live?
Resposta de Travis Bell
no 28 de xuño do 2018 ás 10:24AM
I don't see it happening in the links that @MarcoTC provided. What's an example URL?
Resposta de Jendrik Bertram
no 28 de xuño do 2018 ás 11:06AM
It seems like things are improving, so it might just be a caching issue by now.
When loading this file: https://api.themoviedb.org/3/movie/10378?api_key=123&append_to_response=alternative_titles%2Ccredits%2Cexternal_ids%2Cimages%2Creleases&include_image_language=en%2Cen%2Cnull&language=en you even get "mixed" results. The aspect_ratio for posters is find, but for backdrops it still contains strings. All other numbers seem fine as well.
Resposta de Travis Bell
no 28 de xuño do 2018 ás 11:14AM
Ah yes, that would probably still return a string. We upgraded Ruby, and one of the changes they made in a newer version was to merge their Bignum and Fixnum classes into Integer. The JSON encoder seems to be getting confused now.
I'll look into this more today and report back once I figure it out.
Resposta de Travis Bell
no 28 de xuño do 2018 ás 12:26PM
The fix for this just went live. On any append to response call, the result should be showing the correct values. @jendrik Your query above is now returning proper floats for example.
Let me know if you see this anywhere else.
Resposta de Jendrik Bertram
no 29 de xuño do 2018 ás 1:29AM
Looks like this has done the trick. All responses I have checked seem ok. If anything comes up again I will let you know.
Thanks for the quick fix!