Closed dominicgunn closed 7 years ago
It looks as though some API calls are returning 400s, given the error response (see below). I imagine this is something to do with with the recent update to future times, there appears to be different API instances, running different versions.
➜ ~ curl https://api.dc01.gamelockerapp.com/status {"data":{"type":"status","id":"gamelocker","attributes":{"releasedAt":"2017-08-29T20:17:23Z","version":"v6.8.6"}}} ➜ ~ curl https://api.dc01.gamelockerapp.com/status {"data":{"type":"status","id":"gamelocker","attributes":{"releasedAt":"2017-08-29T18:42:34Z","version":"v6.8.5"}}}
{ "errors": [ { "title": "Bad Request", "detail": "invalid search time" } ] }
Setting the end time filter filter[createdAt-end] to be a minute or two before your current time will avoid this issue.
filter[createdAt-end]
@bguilder You resolved this I believe?
Resolved!
Just a few notes: This is the same issue as #236 It was reverted yesterday due to a bug in the CI/CD pipeline which is also fixed
Bug Details
It looks as though some API calls are returning 400s, given the error response (see below). I imagine this is something to do with with the recent update to future times, there appears to be different API instances, running different versions.
Error Details
Temporary Workaround
Setting the end time filter
filter[createdAt-end]
to be a minute or two before your current time will avoid this issue.