Wsparcie The Movie Database
Wsparcie → Wsparcie API
500 Response
stworzony przez EricSTAFFMOD 26 listopada 2016 o godz. 7:18PM
Searching for a person with parameter aa or tr (just the ones I've found, could be more) results in a 500 Server Error. Have been testing the same query for weeks and have not had similar results with other input values. Full query: https://api.themoviedb.org/3/search/person?api_key={key}&language=en&query=tr
Error:
...rrent/cache/luarocks/share/lua/5.1/lapis/application.lua:396: ...oyed/tmdb-lua-api/current/models/elasticsearch/movie.lua:179: attempt to index field '_source' (a nil value)
stack traceback:
...oyed/tmdb-lua-api/current/models/elasticsearch/movie.lua: in function 'result'
...yed/tmdb-lua-api/current/models/elasticsearch/person.lua:113: in function 'map_known_for_by_ids'
...yed/tmdb-lua-api/current/models/elasticsearch/person.lua:147: in function 'results'
...deployed/tmdb-lua-api/current/applications/v3/search.lua:89: in function <...deployed/tmdb-lua-api/current/applications/v3/search.lua:76>
Traceback:
stack traceback:
[C]: in function 'error'
...rrent/cache/luarocks/share/lua/5.1/lapis/application.lua:396: in function 'handler'
...rrent/cache/luarocks/share/lua/5.1/lapis/application.lua:130: in function 'resolve'
...rrent/cache/luarocks/share/lua/5.1/lapis/application.lua:161: in function <...rrent/cache/luarocks/share/lua/5.1/lapis/application.lua:159>
[C]: in function 'xpcall'
...rrent/cache/luarocks/share/lua/5.1/lapis/application.lua:159: in function 'dispatch'
...api/current/cache/luarocks/share/lua/5.1/lapis/nginx.lua:214: in function <...api/current/cache/luarocks/share/lua/5.1/lapis/nginx.lua:212>
Odpowiedź użytkownika Travis Bell
26 listopada 2016 o godz. 9:56PM
Hi @ericcarboni Good catch. I'll get it fixed in the next day or two.
Odpowiedź użytkownika Eric
26 listopada 2016 o godz. 10:03PM
Thanks for the quick reply! Do you think all possible queries that throw this error will be fixed? Or is it just trial and error?
Odpowiedź użytkownika Travis Bell
26 listopada 2016 o godz. 10:10PM
No problem! They'll all be fixed.