Adri Van Houdt

Bankai: 9.0.0-rc9 Node: 8.9.0 npm: 5.5.1 Didn't even know it was doing ssr /mindblown :D

I also had this issue * pnpm version 7.14.2 (installed via homebrew on macOS 13, but updated over time with `pnpm add -g pnpm`) * run `pnpm env --global 18`...

Probably also need to revert the fixes that were added https://github.com/profoundry-us/material/commit/b294af2bc6f6bedc65b929cc20f3a76ff1090bbc#diff-ff328e798f1dc3e8a2f4dff8e0d639c5R89 But that needs to be checked. What does `target 1.2.0` entail? Do I branch of a specific tag or?

It could be that I added the span to be able to draw those lines, if I did it didn't have a visual impact at the time. The screenshot was...

friendly bump, I think this would be handy to prevent unexpected long queries from eating up resources

I think reverting that `autocommit` will do a lot?

I seems the tests are failing because of linting issues for easiness ;) : ``` js /home/travis/build/felixge/node-mysql/lib/protocol/Parser.js 301:11 error Missing semicolon semi 304:29 error Missing semicolon semi 305:43 error Missing...

I encountered the same issue on joi-phone-number with a `.single`. We solved it with an `alternatives().try` and manual cast to array. See https://github.com/Salesflare/joi-phone-number/blob/1876840415347663bd652077941621cc03d86644/lib/index.js#L37 and https://github.com/Salesflare/joi-phone-number/blob/1876840415347663bd652077941621cc03d86644/lib/index.js#L53 I definitely expected the `.single`...

if @yogyrahmawan is ok with it I can add this to my PR, sure

:+1: