-
-
Notifications
You must be signed in to change notification settings - Fork 136
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
ValueError: not enough values to unpack (expected 2, got 1) #464
Comments
Seems like the issue is here: https://github.com/meraki-analytics/cassiopeia/blame/48184665b79ecda0197b3a31f75f99ba6d462831/cassiopeia/datastores/common.py#L255
I'm guessing the Riot API used to return
|
Hey, This fix works for me. I'm now getting issues when fetching patches but I think that's a whole nother issue concerning how Riot changed their patch naming system. Edit: After testing some more, it seems there may be a deeper issue at hand. Not sure if it's from your fix or is a separate issue that has arisen, but I get an assortment of errors when I try to fetch a variety of different things. Here is an example:
I got these sorts of errors when also fetching match.patch, team.bans, participant.champion, participant.runes, and participant.summoner_spell_d (and f). Sometimes I didn't get the The only common link is that each command that doesn't work is one that calls https://ddragon.leagueoflegends.com/realms/na.json, so I feel as if it has something to do with how it now interacts with datadragon/dto objects. I decided to install the cassiopeia-diskstore plugin to see if it would change anything as per this article but it didn't seem to really affect anything. Again, not sure if this is from your fix or in general. |
Hi,
I have a project in which I am attempting to retrieve match data. This code worked in the latter half of last year, but recently it throws me this error when I try to access a match from match history.
Here is the block I am attempting to run:
And here is the traceback:
I have attempted trying different users, but I still get this. Not sure if I'm doing something wrong, as I'm not too experienced in dealing with APIs. I'm not 100% sure this is something on Cassiopeia's side that broke it, maybe changes in the API? Again, it's not my area of expertise, so I'd appreciate any guidance or help.
Thank you for your time.
The text was updated successfully, but these errors were encountered: