🐛 Bug: 0.109.1 -> 0.109.2 : Migration from 0107004 to 0108002 failed

[wuzhiping]

Migration from 0107004 to 0108002 failed ────────────────────────────────────┐│
││ Error
││ -----
││ TypeError: Cannot read properties of null (reading 'type')
││ at u (/usr/src/app/docker/main.js:1:1368013)
││ at processTicksAndRejections (node:internal/process/task_queues:96:5)
││ at async p (/usr/src/app/docker/main.js:1:1368934)
││ at async Object.t.default [as handler]
││ (/usr/src/app/docker/main.js:1:1369335)
││ at async Function.upgrade (/usr/src/app/docker/main.js:1:1334775)
││ at async InstanceWrapper.useFactory [as metatype]
││ (/usr/src/app/docker/main.js:1:892870)
││ at async Injector.instantiateClass
││ (/usr/src/app/node_modules/@nestjs/core/injector/injector.js:355:37)
││ at async callback
││ (/usr/src/app/node_modules/@nestjs/core/injector/injector.js:56:34)
││ at async Injector.resolveConstructorParams
││ (/usr/src/app/node_modules/@nestjs/core/injector/injector.js:136:24)
││ at async Injector.loadInstance
││ (/usr/src/app/node_modules/@nestjs/core/injector/injector.js:61:13)
││
││
││ Please raise an issue in our github by using following link :
││ https://github.com/nocodb/nocodb/issues/new?labels=Type%3A%20Bug&template=bug_report.md
││
││ Or contact us in our Discord community by following link :
││ https://discord.gg/5RgZmkW ( message @o1lab, @pranavxc or @wingkwong )
││
│└──────────────────────────────────────────────────────────────────────────────┘
| [Nest] 74 - 06/25/2023, 11:22:23 AM ERROR [ExceptionHandler] Cannot read properties of null (reading 'type')
| 0|main | TypeError: Cannot read properties of null (reading 'type')
| 0|main | at u (/usr/src/app/docker/main.js:1:1368013)
| 0|main | at processTicksAndRejections (node:internal/process/task_queues:96:5)
| 0|main | at async p (/usr/src/app/docker/main.js:1:1368934)
| 0|main | at async Object.t.default [as handler] (/usr/src/app/docker/main.js:1:1369335)
| 0|main | at async Function.upgrade (/usr/src/app/docker/main.js:1:1334775)
| 0|main | at async InstanceWrapper.useFactory [as metatype] (/usr/src/app/docker/main.js:1:892870)
| 0|main | at async Injector.instantiateClass (/usr/src/app/node_modules/@nestjs/core/injector/injector.js:355:37)
| 0|main | at async callback (/usr/src/app/node_modules/@nestjs/core/injector/injector.js:56:34)
| 0|main | at async Injector.resolveConstructorParams (/usr/src/app/node_modules/@nestjs/core/injector/injector.js:136:24)
| 0|main | at async Injector.loadInstance (/usr/src/app/node_modules/@nestjs/core/injector/injector.js:61:13)

[WeT-Klb]

I have exactly the same problem on a QNAP-NAS. When upgrading to 0.109.2 the console show this:

[Nest] 12 - 06/27/2023, 6:25:34 AM ERROR [ExceptionHandler] Cannot read properties of undefined (reading 'cn')
TypeError: Cannot read properties of undefined (reading 'cn')
at u (/usr/src/app/docker/main.js:1:1368450)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async p (/usr/src/app/docker/main.js:1:1368934)
at async Object.t.default [as handler] (/usr/src/app/docker/main.js:1:1369335)
at async Function.upgrade (/usr/src/app/docker/main.js:1:1334775)
at async InstanceWrapper.useFactory [as metatype] (/usr/src/app/docker/main.js:1:892870)
at async Injector.instantiateClass (/usr/src/app/node_modules/@nestjs/core/injector/injector.js:355:37)
at async callback (/usr/src/app/node_modules/@nestjs/core/injector/injector.js:56:34)
at async Injector.resolveConstructorParams (/usr/src/app/node_modules/@nestjs/core/injector/injector.js:136:24)
at async Injector.loadInstance (/usr/src/app/node_modules/@nestjs/core/injector/injector.js:61:13)

Only it seems the reason in first line differs from the writer before.
When switching back to 0.109.1 everything works again - but not sure if the data in database already changed something during trying to upgrade.

[pranavxc]

We have fixed the issues in the latest release, please try it out.

When switching back to 0.109.1 everything works again - but not sure if the data in database already changed something during trying to upgrade.

In situations where the upgrader encounters a failure midway, it initiates a rollback process that undoes any changes made. This seamless process occurs because we execute the upgrader within a transaction, allowing for smooth downgrading without any issues. However, it is important to note that downgrading is not feasible if there is a newly added Knex migration present.

[WeT-Klb]

Today i tried the the new upgrade - and it seems all data are still present. At least this time the upgrade worked smoothly.