Internal error while parsing EventSub Prediction event

[VGorku]

Subscriptions and two simple callbacks:

async def test_event(data: ChannelPredictionEvent):
    print('EVENT', data.event.broadcaster_user_id)

async def test_end_event(data: ChannelPredictionEndEvent):
    print('EVENT', data.event.broadcaster_user_id)

subscription_ids['begin'] = await eventsub.listen_channel_prediction_begin(subscription_row['twitch_id'], test_event)
subscription_ids['end'] = await eventsub.listen_channel_prediction_end(subscription_row['twitch_id'], test_end_event)
subscription_ids['lock'] = await eventsub.listen_channel_prediction_lock(subscription_row['twitch_id'], test_event)

What I did is that simply created Prediction on Twitch (everything was fine) and closed submissions right after that. Seems like it's failed upon parsing the Lock event https://dev.twitch.tv/docs/eventsub/eventsub-subscription-types/#channelpredictionlock

Sorry for the screenshot, that's all I got for now

Any suggestions on how to fix that? Thanks <3

[VGorku]

I think I got it.

I was testing off-stream, basically starting Predictions and ending them without any vote. It seems that current implementation does not expect data['event']['outcomes']['top_predictors'] to be empty list:

Here is my disgusting workaround in twitchAPI/eventsub/webhook.py if someone interested (I dont need top predictors for my project)

Hope this will be fixed 🤞

[Teekeks]

I cant reproduce this by starting a prediction & then either letting it run out or closing it manually without anyone voting.

Could you please provide the following for further investigation:

• Your used Python Version
• The Version of the Library you are using
• An exact step by step guide of how to reproduce this
• A code example that will reproduce this

[Gregorein]

@Teekeks, I think this may be related to my issue, as I'm also having problems with TopPredictors being handled incorrectly in a prediction.end event

However issue occurs in websocket, not webhooks

https://github.com/Teekeks/pyTwitchAPI/issues/315

[Teekeks]

Fix for this is now available on pypi in v4.2.1. Was not able to reproduce because I already fixed that locally...