insidewhy

Results 151 comments of insidewhy

@orthecreedence on archlinux and Ubuntu, both with zero iptables rules set up before running rkt. As far as I can tell rkt is just for clusters and from squeed's comment...

Also started a PR to try to fix the code but got zero support or even acknowledgement... on such a key issue. Doesn't give me much faith in rkt.

I have `iptables -P FORWARD ACCEPT` already but I still see this issue.

@iaguis I switched them but it makes no difference. Also whether whether you use `-n` or not you see `any` for the SNAT `source` and I see `127.0.0.1`.

It's the same for other classes too, like AggregateFunctions etc. In fact the only place this code is using `prototype` is in the drivers. 👎

Even if that were the case it's still a terrible reason for making every non-property instantiated in the constructor. This is some of the worst performing code I've used in...

Setting the default value feels like overreach for me. I've installed pre-git in about five projects now and never wanted it.

pre-git should be modular and do one thing well. Commit message validation should be a separate package.

Released this package which supports wildcards in mocks and a bunch of other nice functionality to help writing tests: https://github.com/insidewhy/wildcard-mock-link Is documented/tested.

@richardwu you should use reactions instead of comments saying +1 which notify all thread watchers. At any rate wildcard-mock-link already supports this together with all other features of the mock...