TypeError: __init__() got an unexpected keyword argument 'vod_offset'

[rkamogh]

Here is the code
warning:root:No model for prediction available -> every clip is chosen as valid (ingame)
Traceback (most recent call last):
File "main.py", line 17, in
ch.get_clips(
File "C:\Users\Amogh\Desktop\TwitchCompilationCreator-2.0\src\ClipHandler.py", line 46, in get_clips
self.get_game_clips(utils.get_headers(), timespan, language, kwargs)
File "C:\Users\Amogh\Desktop\TwitchCompilationCreator-2.0\src\ClipHandler.py", line 78, in get_game_clips
self.handle_response_data(resp.json(), language, creator_counts, filter_information)
File "C:\Users\Amogh\Desktop\TwitchCompilationCreator-2.0\src\ClipHandler.py", line 136, in handle_response_data
current_clip = Clip(**clip)
TypeError: init() got an unexpected keyword argument 'vod_offset'
then it stops working

[lucaSchilling]

Hey, have you installed everything via porety Install? It looks like a dependency has a newer versuon that it should have.

[rkamogh]

Yes i have installed everything via poetry install but it also asked me to update afterwards and so I did. Is there any way to revert this however?

[lucaSchilling]

Yeah ja restore the original pyproject.toml and poetry lock abd then run portey install again.

[rkamogh]

how do i restore the original pyproject.toml and poetry lock

[lucaSchilling]

If you are using git discard your changes you can google how to do that. Otherwise just download those two files and replace them in the project folder or edit those two files and copy paste the content from our repository into them.

[rkamogh]

i replaced the files and it still has the same error. I am on version 2.0 by the way.

[lucaSchilling]

Have you eun poetry install after replacing them? What program do you mean by 2.0?

[rkamogh]

The 2.0 version of this repository and I have run poetry install after replacing them

[lucaSchilling]

Can you run poetry show and post a screenshot of what dependencies are installed in your environment?

[MorMundHS-MA]

@OPgamemasterYt Twitch updated their API including a new property in their response. We fixed this issue so after a pull it should now work as expected. Thank you for reporting this issue!

[rkamogh]

how do i fix it?