Skip patches howto

[info]

Hi there,

trying to upgrade from an old version like 6-9 can be a problem. In this thread for example is advised just to skip patches:

Upgrading ERPNext Version 6-9

For those old users who need to do this and may have failed in the past, here’s a step by step that works. Upgrade steps for anyone moving from an old version like 6 or 7 SO… head to the terminal and navigate to frappe-bench folder, prompt should look like frappe@erpnext:~/frappe-bench$ install psutil if absent or fails… sudo pip install psutil remove nodejs, sudo apt-get remove nodejs install nodejs v6 or v8, the newer the better – install curl, do… sudo apt-get install curl if you ha…

On the other hand, it is not recommended:

How to skip patch application if its faulty?

Hi, Many times when we are using bench update in the development environment we get to see bugs in some patches which basically renders the test system useless till the patch is corrected for errors. I was wondering if it would be possible to skip a patch till the time its fixed. Please note I know a work around by adding the patch in the patch log table but it seems tedious as we would have to do that at the backend (mysql) as the local system would be in the UPDATING… STATUS. Is there any o…

Any advice on how to handle with errors in patches when upgrading?

[noetico]

Well it depends on the patch in question, If you look at the patch title you can tell if it’s critical to functionality of key modules and documents. We see the bugs mostly with what I may call ‘social’ features.

In more than 5 to 6 upgrades I’ve had to skip well over 12 patches each time and the upgrade always finishes.

Sent from my BlackBerry 10 smartphone.

[info]

Thank you for your answer. But then when skipping patches, bench update complains that the version in server is modified and is stopping the update also.

On the other hand, when running bench update --reset then all commented patches are uncommented and the problem persists.

Which way is best in your opinion to run the update command and keep the changes in the patches.txt file?

[noetico]

Sorry for a month old reply, to prevent a new patches.txt, proceed with bench migrate

[aakvatech]

bench migrate --skip-failing does the job.

However, it would be good to run
bench update
after it’s done.

[noetico]

Nice, is this a new addition. brilliant, will keep this in mind before now this was manual.

[nathan_dole]

@aakvatech

bench update

Will it try to resolve the failed migrations ? In other framework there is a sqldiff to provide what is missing between the database state and the code, is something similar available in frappe ?

[aakvatech]

It will do the sqldiff and attempt to resolve. If it fails then there it would be because of unresolvable situatoin.

[nathan_dole]

in that case is there a way to show the result of the sqldiff so that we can try to resolve manually ?

[aakvatech]

Check the traceback and post here.

[nathan_dole]

Thank you!

I got it upgraded to v13. Will take sometimes to share the experience migrating from 7 to 13 later.

Just a small question, currently I cannot see the Exception error anymore in frappe.log. All it shows is:

2021-07-24 06:21:44,686 ERROR frappe New Exception collected with id: 2021-07-24 06:21:44.191117-115.74.40.215-969

Just update my developer_mode to 1 but nothing new yet

[nathan_dole]

After further digging, found that in error-snapshots Logging

Thanks

[ngoploti]

you have saved my life brother.