Closed bosim closed 5 years ago
Hi @bosim,
Yes, it is intentional, but if we want to check the necessity of upgrading to changes all the way back to 2014 it does takes too long particularly for the check you mention. We could run the test via the controller and cache the output, or limit the amount of tests to only the most recent steps. I've noticed the issue too and it caused issues with automatic monitoring of TCAT instances.
For now, no warnings are displayed in the backend for upgrade steps which were added prior to May 2018 (in other words: none). Ofcourse upgrading using the cli
method still works.
Nice change. Thanks for fixing.
capture/index.php
contains$tests = upgrades(true);
which, even in dry_run mode, is costly. Especially the query below is very costly.
I wonder why the dry_run check is run everytime
capture/index.php
; just for convenience?