Krishna Raj K

Same for me too. Issue re-appeared a few days back. Reversed the previous fix (which is suggested by @xHasKx) and fixed the issue.

Temporary fix. edit `~/.atom/packages/atom-ctags/node_modules/ctags/src/ctags.coffee` and in the first line `{Tags} = require(process.resourcesPath + '/app/node_modules/ctags/build/Release/ctags.node')` change `app` to`app.asar.unpacked`, which becomes `{Tags} = require(process.resourcesPath + '/app.asar.unpacked/node_modules/ctags/build/Release/ctags.node')`

@michaelczhou If you are using linux, try `locate ctags.node` in terminal to find the location of the node package. use that location in the coffee file.

But my point is that the migrations works fine with MySQL 8.0 without setting the default string length as 125 or updating the migrations, when using InnoDB with dynamic or...

I couldn't find any query to get the configuration. But as you might already know, the engine and row format can be obtained from the information schema. Maybe that details...