Errors appeared after upgrading mysql from 5.6 to 5.7 with homebrew on Mac OS X Sierra

mysql_error.txt

2018-07-26T14:39:33.6NZ mysqld_safe Logging to '/usr/local/var/mysql/P40902.err'.
2018-07-26T14:39:33.6NZ mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql
2018-07-26T14:39:34.247649Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2018-07-26T14:39:34.248430Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2018-07-26T14:39:34.248520Z 0 [Note] /usr/local/opt/mysql@5.7/bin/mysqld (mysqld 5.7.22) starting as process 35936 ...
2018-07-26T14:39:34.256969Z 0 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive
2018-07-26T14:39:34.259865Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-07-26T14:39:34.259896Z 0 [Note] InnoDB: Uses event mutexes
2018-07-26T14:39:34.259907Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2018-07-26T14:39:34.259917Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-07-26T14:39:34.260420Z 0 [Note] InnoDB: Number of pools: 1
2018-07-26T14:39:34.260598Z 0 [Note] InnoDB: Using CPU crc32 instructions
2018-07-26T14:39:34.264645Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2018-07-26T14:39:34.287216Z 0 [Note] InnoDB: Completed initialization of buffer pool
2018-07-26T14:39:34.347833Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4000!
2018-07-26 23:39:34 0x7fff9e6653c0  InnoDB: Assertion failure in thread 140735850894272 in file ut0ut.cc line 942
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
14:39:34 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68220 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x40000
0   mysqld                              0x00000001012cf5da my_print_stacktrace + 58
1   mysqld                              0x000000010124efe9 handle_fatal_signal + 700
2   libsystem_platform.dylib            0x00007fff9595db3a _sigtramp + 26
3   ???                                 0x0000000100000001 0x0 + 4294967297
4   libsystem_c.dylib                   0x00007fff957e2420 abort + 129
5   mysqld                              0x00000001014ac43a _Z23ut_dbg_assertion_failedPKcS0_m + 161
6   mysqld                              0x00000001014aee86 _ZN2ib5fatalD2Ev + 88
7   mysqld                              0x00000001014aeebf _ZN2ib5fatalD1Ev + 9
8   mysqld                              0x0000000101360b79 _ZL18fil_node_open_fileP10fil_node_t + 2419
9   mysqld                              0x0000000101369d16 _ZL23fil_node_prepare_for_ioP10fil_node_tP12fil_system_tP11fil_space_t + 191
10  mysqld                              0x000000010136a3bf _Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_ + 798
11  mysqld                              0x0000000101332d42 _ZL17buf_read_page_lowP7dberr_tbmmRK9page_id_tRK11page_size_tb + 384
12  mysqld                              0x0000000101332e96 _Z13buf_read_pageRK9page_id_tRK11page_size_t + 59
13  mysqld                              0x000000010131f8f2 _Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb + 1838
14  mysqld                              0x000000010149d7bb _Z31trx_rseg_get_n_undo_tablespacesPm + 254
15  mysqld                              0x0000000101481107 _Z34innobase_start_or_create_for_mysqlv + 6828
16  mysqld                              0x00000001013b874d _ZL13innobase_initPv + 3700
17  mysqld                              0x0000000100d3cb99 _Z24ha_initialize_handlertonP13st_plugin_int + 79
18  mysqld                              0x00000001011a07cb _ZL17plugin_initializeP13st_plugin_int + 79
19  mysqld                              0x00000001011a02dc _Z40plugin_register_builtin_and_init_core_sePiPPc + 659
20  mysqld                              0x0000000101244aac _Z11mysqld_mainiPPc + 2942
21  libdyld.dylib                       0x00007fff9574e235 start + 1
22  ???                                 0x0000000000000006 0x0 + 6
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
2018-07-26T14:39:34.6NZ mysqld_safe mysqld from pid file /usr/local/var/mysql/P40902.pid ended