Houston, We Have A Problem!

Sort:
stephen_33

I've been trying to download the match archive for this club ...

https://www.chess.com/club/chess-school 

..but I keep getting an HTTP 500 error. Although the club has a history of playing matches, it seems the endpoint isn't available? At least that's what I'm seeing when I enter the URL into the address bar of my browser...

https://api.chess.com/pub/club/chess-school/matches 

I receive back...

{"status":"error","message":"Internal Server Error"}
Magnus_Chase19

oof

WhiteDrake

That's interesting. surprise.png 

l3thalcs

Just went through the documentation. If you check the endpoint https://api.chess.com/pub/club/chess-school , the value of visibility is "private". Maybe that is the reason why its showing a 500 error. I tried with the chess developer community club's endpoint which is a public group and its giving the desired response. (https://api.chess.com/pub/club/chess-com-developer-community/matches)

Edit: My bad. Tested it out with another private club and it is showing the desired response as @APISTOTELHS pointed out.

APISTOTELHS
l3thalcs έγραψε:

Just went through the documentation. If you check the endpoint https://api.chess.com/pub/club/chess-school , the value of visibility is "private". Maybe that is the reason why its showing a 500 error. I tried with the chess developer community club's endpoint which is a public group and its giving the desired response. (https://api.chess.com/pub/club/chess-com-developer-community/matches)

This is not the problem thought! If you test any club with "private visibility" it will work.

bcurtis

This club has sooo many matches and other details that our servers run out of memory before they can deliver the data. It's not an easy fix. I'll ticket it, but right now I do not expect the manpower to address this soon. Apologies for the inconvenience.

stephen_33
bcurtis wrote:

This club has sooo many matches and other details that our servers run out of memory before they can deliver the data. It's not an easy fix. I'll ticket it, but right now I do not expect the manpower to address this soon. Apologies for the inconvenience.

Appreciate the explanation & I'll find a work-around.

Is it reasonable to assume this will correct itself as soon as a match in that club changes its status, or a new one is created & the endpoint is refreshed?

bcurtis

Without an investigation, it's difficult to know what parts of the data gathering are hogging the RAM. So I cannot predict that, but what you describe is possible.