Olga Shestopalova

>There's no v18 yet, which specific commit / sha is this? Hi, this is from commit [e7c0bb07ac](https://github.com/vitessio/vitess/commit/e7c0bb07ac0b5c0ddd2dfa2da5a1bfb2a25bae4a), I pulled from main a couple of days ago

I'm encountering something very bizarre. I made the fix in v18 to not have that extra convert and it's a valid mysql query and yet: `failed inserting rows: Cannot create...

Huh, I need to go back and retry my v18 migration then. I only have tablets in v18, not vtgates or vtctld, but that shouldn't matter because vreplication/onlineddl is all...

I'll also test out that workaround Rohit suggested

Ok so I tested with mysql 8 and my migration worked, even the v14 version, and also Rohit's workaround works (with 5.7 and v14) - but would require us to...

I see, that would be quite difficult for us to implement because we'd have to run migrations (non-vitess) on every table that has a json column and a generated column...

Heh I found another bug with JSON, though unrelated to this: https://github.com/vitessio/vitess/issues/14089

I have two samples of mpstat data from two different hosts, taken every second, starting from several minutes before the hosts had an ENA driver reset until the reset: https://gist.github.com/olyazavr/ae46c0a7315e96580a516d8bf9b2a498...

The first one (ip-172-18-82-184.ec2.internal) is i-05144ca77bafd3229. The second (ip-172-18-65-61.ec2.internal) is i-07c1e144193d42f25. Both are in us-east-1

👋 We're upgrading from 1.6.x to 1.7.23 and this is spamming the logs, would love a fix here