Show newer

@saper trying to db:migrate:down 20171028221157 fails because show_reblogs doesn't exist

trying to db:migrate:up 20171028221157 returns nothing because show_reblogs already exists

@saper the error is that rails says Follow and FollowRequest neither have :show_reblogs

while in the DB both follows and follow_requests tables have "show_reblogs" columns

@saper 20171028221157

but db:migrate:status shows all of them up to the latest one as of 2.1.0 up

@troubleMoney follow in ruby shows :show_reblogs attribute

follow_request doesn't

both tables have it on db

@InspectorCaracal @Gargron unlisting emoji and later features all work fine so THOSE migrations were done as well

do i just add all timestamps to the column or what like i don't understand what i need to do now

our schema_migrations table is not complete

@Gargron @InspectorCaracal our latest migration row is 20171020084748 Feature: Unlisted custom emojis (#5485)

the one in the codebase right afterwards is 20171028221157 Allow hiding of reblogs from followed users (#5762)

so do i just add that timestamp to our migration list and try to db:migrate again? is that what you're telling me to do?

@Gargron @InspectorCaracal how do we do that? i do not know how the schema_migrations table works. is it documented anywhere

@Gargron @InspectorCaracal i do not want to do this. if we absolutely have to then let's do it soon rather than later. but i do not like this option. is there seriously no other way

@daHob @InspectorCaracal @Gargron table follow_requests in the database has column show_reblogs properly set up. rails model FollorRequest has no :show_reblog attribute.

@Gargron @InspectorCaracal @daHob InspectorCaracal did our migration from 2.0.0rc3 to 2.1.0. We've done database migrations before restarting rails. Apparently something went wrong along the way and we have no clue what.

@Gargron @InspectorCaracal @daHob we have restarted rails, following still causes 500. talk to me eugen what am i doing wrong here

@troubleMoney @InspectorCaracal no i meant

the columns are already present in the db

ruby doesn't know they're there

Show older
Computer Fairies

Computer Fairies is a Mastodon instance that aims to be as queer, friendly and furry as possible. We welcome all kinds of computer fairies!