HTTP 504 on certain player match requests

[turindev]

Some players get a timeout when requesting specific pages of matches (HTTP 504 Gateway timeout). Here is an example:

https://api.dc01.gamelockerapp.com/shards/na/matches?page[offset]=100&filter[playerNames]=Bearthc&sort=createdAt&filter[createdAt-start]=2017-12-05T18:00:00Z&filter[createdAt-end]=2017-12-25T03:57:08Z

After further digging, it looks like match #129 specifically is causing the failure.

[ghost]

Yup. I see 502's and 504's randomly.

27-12-2017 (Wed) 16:48:16 Server HTTP Error: 504 https://api.dc01.gamelockerapp.com/shards/na/matches?filter[playerIds]=20777044-e22e-11e7-9e46-06c70774b11e&filter[createdAt-start]=2017-12-15T00:00:00Z&page[offset]=100&page[limit]=50

[jaloisi834]

Thank you for the report, however, we ask that you please use the "report a bug" interface on the developer portal (or email vainglory-gamelocker@madglory.com directly) to submit issues going forward. This will help us keep things organized on our end, and we really appreciate it.

Anyways, this is definitely weird, and we are looking into it ( and tracking internally).

[ghost]

Could we please get some kind of read only access to the internal issue tracker? Maybe for developers having API rate limit > 50 or something (since they are manually verified). It is very difficult to know the status of bugs for us as community devs. We don't know if everyone is facing the issue or it is just a single developer. We don't know if the bug was successfully reported at all. There is no issue history on the "report a bug" interface.

It will save us time and save you guys time too to prevent duplicate issues.