bughit

This appears to be more than just a warning, ssl_mode config does not work. To build mysql2 on debian buster requires [default-libmysqlclient-dev](https://packages.debian.org/buster/default-libmysqlclient-dev) which is maria based. Also, where is HAVE_CONST_MYSQL_OPT_SSL_ENFORCE...

looks like #4 enables this, do you plan on merging it?

@brianhempel, what do you think of #4?

both ``` ruby User.where(id: 1).where.any_of(User.where(id: 2), User.where(id: 3)) User.where(id: 1).merge(User.where.any_of({id: 2}, {id: 3})) ``` are correct, producing ``` sql SELECT `users`.* FROM `users` WHERE `users`.`id` = 1 AND (`users`.`id` =...

updated example to better illustrate the problem

the default binding value should be TOPLEVEL_BINDING.dup ```ruby def result(_binding_or_hash=TOPLEVEL_BINDING) _arg = _binding_or_hash if _arg.is_a?(Hash) _b = binding() eval _arg.collect{|k,v| "#{k} = _arg[#{k.inspect}]; "}.join, _b elsif _arg.is_a?(Binding) _b = _arg...

What's needed here is the ability to specify additional opts to `http_client.start` which will be applied to the client instance before connecting.

I'm guessing from your links you're going to suggest to supply a custom unformatter? That's not a reliable solution to a problem that should not exist in the first place....

@hackademix Did you intentionally remove the "trusted with some untrusted" state ()? Don't you think it's helpful to know from the icon if all domains are accounted for?

it appears that the meaning of frame permission changed from the classic version, the new meaning seems to be focused on the destination and not the origin of the request:...