Paul Campbell

@tbouron I've updated the `Jenkinsfile` as requested.

retest this please

@ClearlyClaire No. I completed the steps in order. I've repeated the process (after restoring from backup) and it still shows the same error.

No errors reported during either the pre-/post-deployment migrations. I tried the `tootctl` command both before and after the upgrade. I'm still seeing the same oops screen and log error.

I've tried having a look at the Users table. (log) ``` # su - mastodon $ cd live $ psql mastodon_production mastodon_production=> \d users Table "public.users" Column | Type |...

No, this is a single server setup. `$ RAILS_ENV=production bundle exec rails db:migrate:status ` (output) ``` database: mastodon_production Status Migration ID Migration Name -------------------------------------------------- up 20160220174730 Create accounts up 20160220211917...

I suspect I messed up when I was first installing my instance (wow is it only two weeks ago?). I tried v4.0.0rc2 but ran into problems so backed of to...

I've been able to upgrade my test instance to v4.0.0rc3. Mostly my resetting the `schema_migration` table as you suggested and then commenting out offending lines in the `db/migrate/*` and `db/post_migrate/*`...

@mre I'd assume the most people learning/developing Rust would know how to create their own fork. I like your idea of adding them to https://corrode.dev/idiomatic-rust/ though. That's even less friction...

I can certainly give it a go. Let me get my current project squared away and I can look at it then. I used `gitoxide` a little in `git-next`, but...