gubbins

The panic always seemed to occur at the same point - fetching standup config for channel with id `tass9ycqbfrrdp4ms34z834wac`. I don't know how to inspect the standup config of that...

I'm looking, but not finding anything that looks relevant. Would it have required debug-level logs? We did not have debug logs enabled at the time of the upgrade.

Looking further back, I see occasional instances (before we upgraded) of: ``` dpanic [email protected]/sugar.go:191 Ignored key without a value. {"plugin_id": "standup-raven", "ignored": "Error occurred processing /standup"} ``` and sometimes randomly...

With a local build of the plugin I was able to print the JSON of the standup `Config` for one of the breaking channels: ```json { "channelId": "tjwshcz8gfyupk8h93t8yyuhir", "windowOpenTime": "15:00",...

I think I will try forcing the database version back to 2.0.0 and letting it try the upgrade again.

That seems to have worked. I wonder if the issue here is that the plugin was downgraded at some point.

Looking at this further (for mysql), I realised that if the number of enum values is the same, then changes in the list of possible enum values are detected -...

Interestingly I tried changing the demo to use Ctrl instead of Shift and it seems to work just fine. I guess some confusion over horizontal scrolling?