127 karma · joined October 2, 2014
Unlike the JAK inhibitors that suppresses the immune system, their pill instead resolves the inflammation by activating receptor 1 and 3 in the melanocortin system. Phase 2b completes this summer and I am personally super excited to see the results.
We did a dirty solution for this with Ansible. We have a base playbook (with roles and all that jazz) that sets up a server and then we can write patches which are separate playbooks.
After the patch has run we simply store the patchlevel in a file on the server so that we dont "double-apply" any patches on the next patch-run.
I think this is a very vocal minority in play here. From my understanding these changes did not come from any of the core contributors but rather from activists. The used divide and rule; if you don't sign off on our political documents you are with "them" and we will let everyone know what a horrible human being you are.
The kernel project is surely one of the most successful software projects ever. Having survived for 20 years, why change a winning formula?
I have always considered Linus un-political and more interested in getting sh*t done and getting it right above anything else, so why he would sign-off on this is a mystery to me.
Btw, what is missing in the invoices?
For us to be able to move from S3 we would also need to be able to create multiple API keys where we can set what buckets they have access to.
It has been fixed now: http://wpdetective.io/www.berghs.se
We collect this information from the WordPress plugin repository but it only contains free plugins. Paid plugins are not listed in a central place where we query their metadata.
There are some very popular plugins (Yoast SEO, Jetpack, W3 Total Cache) that don't import additional files. For these we have hardcoded patterns (under a 100). We do not have anything in place for checking if these patterns break.
We could automate creating a WordPress installation, installing the plugin we want to check, trigger a wp detective scan and then checking the results. But I am note sure it is worth the engineering effort.
WordPress have a predictable path structure and we use that to extract theme and plugin slugs (textual ids). For some plugins that don't import JS or StyleSheets we look for other signatures.
Once we have the slugs, we do a lookup in the official WordPress theme/plugin repository and get all the info we need (plugin descriptions, icon, author etc)
You assume correct, that is one of the methods we are using.
We also look for signatures in the code that certain plugins output. For example Yoast SEO usually adds a HTML comment at the end of the page identifying itself.
Isn't that quite contradictionary?
You can even add a little notice in your email signature that this is how you operate.
Some of the highlights:
- GCC is no longer installed by default on architectures where clang(1) is the default compiler.
- Unbound has been imported to the base system as the local caching DNS resolver.
- BIND has been removed from the base system.
- make(1) has been replaced with bmake(1), obtained from the NetBSD Project.
- pkg(7) is now the default package management utility.
- pkg_add(1), pkg_delete(1), and related tools have been removed.
- Major enhancements in virtualization, including the addition of bhyve(8), virtio(4), and native paravirtualized drivers providing support for FreeBSD as a guest operating system on Microsoft Hyper-V.
- TRIM support for Solid State Drives has been added to ZFS.
- Support for the high-performance LZ4 compression algorithm has been added to ZFS.
Full details: https://www.freebsd.org/releases/10.0R/announce.html