I took a look at your logs and saw the following
2020-03-13 15:31:36 Morgan ... DB_COLLATION 66 tables converted.
2020-03-13 16:15:56 Morgan ... DB_COLLATION 66 tables converted.
2020-03-13 16:23:49 Morgan ... DB_COLLATION 66 tables converted.
2020-03-13 17:27:20 Morgan ... DB_COLLATION 66 tables converted.
2020-03-13 18:26:24 Morgan ... DB_COLLATION 66 tables converted.
2020-03-13 18:32:46 Morgan ... DB_COLLATION 66 tables converted.
2020-03-13 21:07:47 Morgan ... DB_COLLATION 66 tables converted.
2020-03-13 21:23:55 Morgan ... DB_COLLATION 66 tables converted.
2020-03-14 07:08:30 Morgan ... DB_COLLATION 66 tables converted.
Those 9 lines tell me that the table conversion was run and completed 9 times.
1st time, latin1_swedish_ci to utf8mb4_general_ci
2nd time, utf8mb4_general_ci to utf8mb4_general_ci
3rd time, utf8mb4_general_ci to utf8mb4_general_ci
4th time, utf8mb4_general_ci to utf8mb4_general_ci
...
9th time, utf8mb4_general_ci to utf8mb4_general_ci
I dont see this as being a problem, since its just taking the current data collation and replacing it with itself.
What I do see as a problem is the following:
Safari failed to keep the communication open between your computer and the webserver. So while your webserver was still running and processing data updates to be sent to your screen, Safari already closed the communication and stopped displaying those updates to you. Safari timed out before the communication was complete.
Your admin log files say the task finished successfully, but Safari prevented the real-time display of that important bit of information from getting to you.
Maybe there is an updated Safari version which resolves that? If not, my advice would be to upgrade to a modern browser.
