-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: /players is seriously out of date #151
Comments
More than rate limit, we would need 10 calls to get a user. That's going to be awefully slow. |
http 'https://api.dc01.gamelockerapp.com/shards/eu/players' "Accept":"application/json" "X-Title-Id":"semc-vainglory" "Authorization":"" "filter[playerNames]"=="jokerq1"
# error 404
http 'https://api.dc01.gamelockerapp.com/shards/eu/matches' "Accept":"application/json" "X-Title-Id":"semc-vainglory" "Authorization":"" "filter[playerNames]"=="jokerq1" "filter[createdAt-start]"=="2017-04-01T00:00:00Z" | jq ".data|length"
# 15 matches
http 'https://api.dc01.gamelockerapp.com/shards/eu/matches' "Accept":"application/json" "X-Title-Id":"semc-vainglory" "Authorization":"" "filter[playerNames]"=="shutterfly" "filter[createdAt-start]"=="2017-01-01T00:00:00Z" "sort"=="-createdAt" "page[limit]"==1 | jq ".included[] | select(.attributes.name == \"shutterfly\") | .attributes.stats.wins"
# 560 wins
http 'https://api.dc01.gamelockerapp.com/shards/eu/players' "Accept":"application/json" "X-Title-Id":"semc-vainglory" "Authorization":"" "filter[playerNames]"=="shutterfly" | jq ".data[].attributes.stats.wins"
# 544 wins |
All set! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
/players
endpoint has not seen an update since about 2017-03-15 on all players.Compare with any result of
/matches
and see that the stats are up to date on the most recent match.This is a critical bug, we are trying to migrate in regard of #145 and this is blocking our production release because we cannot serve new users without ugly workarounds that bust the rate limits.
The text was updated successfully, but these errors were encountered: