update: no codename for pattern_code rule

[Lapizistik]

I tried to update decko from 0.6.8 (to 0.8.0) and the decko update step failed with no codename for pattern_code rule. See attached file for the update log.
decko-update.log

[ethn]

Thanks for letting us know and for including the log!

The log surprises me, because it looks like the migration successfully finishes despite the error. What happens if you run decko update again?

[Lapizistik]

I tried it several times (I must confess I am not sure my first post contained the logfile of the first run. I could try to reproduce this with some effort if needed).
update2.log

[Lapizistik]

So, I rerolled everything back to 0.6.8 (using the backup of the database) and tried it again (full log:
update-script.log ).
Should I try anything else?
Additional information: I am using postgres 11.

[ethn]

Hmm, interesting. Same pattern (migration completes despite errors) but with a different migration.

If have seen this issue with some caching issues before. Are you using file caching? Memcached?

In any case, I would try clearing your cache. And if you have a backup from before you started the migrations, I would start from that, because I'm worried these migrations are getting recorded as having successfully completed.

I assume this is a private data set, but if it's not, and you're able to send a database dump to info@decko.org, I would be willing to see if I can learn anything more about what's going on.

[Lapizistik]

I am not aware of any caching. Which kind of caching do you mean?
The log above was created by starting with the original state of the database (from my backup).
It's kinda private data but I will see whether I can provide you with a copy.
(trying to access the upgraded decko with the browser kinda works but with broken elements, I would have to investigate this further if it helps you)

[Lapizistik]

Next try.
I started with my decko 0.6.8 setup with a blank database and tried to update (see
blank-update.log ).
Problem still exists (so it is not caused by my database contents).

[ethn]

Sorry so slow on this.

We have a new release coming out very soon that has some new error handling that could help. If we don't learn anything new from that, I'll try to mimic your setup – it's certainly interesting that it's happening with a new deck. We do continuous integration testing with postgres, but that doesn't test migrations, and the sites we use most use mysql, so I suppose it's possible there's a blindspot there.

Thanks for investigating and for being so patient.

[Lapizistik]

Thanks a lot for your efforts!
I'll wait for the new release.

I can try to replicate the setup with mysql, if this helps.
There seem to be some changes coming with postgres 11, found several error reports with other software about this, so maybe I should check whether it works with postgres 10.

Take your time.

[ethn]

Actually, yes, knowing whether the error is there with the same setup but with mysql would be very informative. Thank you!

[Lapizistik]

I replicated everything with mariadb (with empty database), and got:

[…]
Your database is not ready to be migrated to 0.8.0.
You will need to do incremental upgrades.                                       
Please first install version 1.6.1 and run `rake db:migrate`.                   
Then install version 1.8.0 and run `rake db:migrate`.                           
                                                                                
Sorry about this! We're working to minimize these hassles in the future.
/var/lib/gems/2.5.0/gems/card-1.98.0/db/migrate/20110511221913_require_earlier_migrations.rb:7:in `up'                                                          
[…]

[ethn]

0.8.1 is out now. I created a new deck with mysql and didn't see any problems.

Can you see if anything changes now? When you tested mariadb, did you run decko seed?

[Lapizistik]

I created a brand new 0.6.8 decko with mariadb (using the mysql2 gem) and then tried to update it. This still fails, see update-mariadb.log
The log should show all steps and you should be able to reproduce this. If I can help any further please tell me.
Thanks for your work!

[ethn]

I'm able to reproduce that! After it fails, if I run decko update again, everything seems to be fine. May be straightforward to fix.

Are you still getting the same problems migrating your real database?

[Lapizistik]

There are still problems with postgres.
Again I started with a brand new decko, this time with postgres11 (using the pg gem) and then tried to update it. This fails, and rerunning the decko update part does not help, see
update-postgres.log

There were some reports on the web about changes between postgres 10 and postgres 11 that caused errors (in particular “ERROR: column "proisagg" does not exist […]”), but I do not know whether this is related.

I could try to create a setup with postgres 10, but this would be a bigger effort.

[ethn]

A quick, not-super-informative update:

I'm now reproducing the postgres error. Tricky so far, but I hope to get a fix out soon.