You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Whenever I try using match.py with match id =729303. it's throwing error: Expecting value: line 1 column 1 (char 0).
It's a valid match ID. I haven't got any issue for other match ids so far, but this one is throwing an error.
On deep diving, I found out that:
json_url = "https://www.espncricinfo.com/matches/engine/match/{0}.json".format(str(match_id))
This is giving: error 500 Internal Server Error
I tried json_url for other match ids and it's giving proper json object.
I don't know what's causing the issue with this match. Is it any server-side issue or am I doing something wrong?
To Reproduce
-> m = Match(729303)
-> m.json
Expected behavior
Match(729303) should work without any error.
Screenshots
Actual Error:
JSON_url for match_id =729303 (NOT WORKING)
JSON_url for match_id =729301 (WORKING)
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
Whenever I try using match.py with match id =729303. it's throwing error: Expecting value: line 1 column 1 (char 0).
It's a valid match ID. I haven't got any issue for other match ids so far, but this one is throwing an error.
On deep diving, I found out that:
json_url = "https://www.espncricinfo.com/matches/engine/match/{0}.json".format(str(match_id))
This is giving: error 500 Internal Server Error
I tried json_url for other match ids and it's giving proper json object.
I don't know what's causing the issue with this match. Is it any server-side issue or am I doing something wrong?
To Reproduce
-> m = Match(729303)
-> m.json
Expected behavior
Match(729303) should work without any error.
Screenshots
Actual Error:
JSON_url for match_id =729303 (NOT WORKING)
JSON_url for match_id =729301 (WORKING)
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: