Open mattyg opened 2 years ago
Some workarounds to fix the migrations -
Util.cleanContent()
:
This ensures that the bot never has to query the channel in which praise was sent, resolving the issue we're having above. And. this also allows us to realise the content better by ensuring that all user ids get rendered irrespective of them having access to that channel.
ORUtil.cleanContent
and use our own implementation that internally queries the data from the Guild object.
Failed Deployment Post-Mortem
reasonRealized
for all existing praise -- by replacing discord's machine-readable formatting of users and channels with human-readable formattingreasonRealized
for all existing praise topraise.reason
.Log of failed migraiton
Research
948663379487252530
Omega > Consilience library
/praise
command inside a thread currently (see image below)Reflections
In the future we might want to change how we handle failed migrations:
When a migration fails on deployment, revert to the previous deployment. Currently the process would be:
yarn run migrator down
(for each new migration)Additionally, it might be easier if we squashed multiple migrations into one, for any release that has multiple migrations. That way, the process to revert to a previous deployment would be: