Greg Weber

Can we create a new `RootCause` function and deprecate the existing `Cause` function? That will satisfy backwards compatibility. `Cause` would only be dropped in a breaking release.

It would just fix this bug.

Does it help to use `causer` instead of `Cause` for the type assertion to only go one level deep?

This change is problematic because it changes backwards compatibility and somebody else actually wants it this way. On our [fork of pkg/errors](https://github.com/pingcap/errors) we [added new functions](https://github.com/pingcap/errors/pull/2/files#diff-dd25e0e0a594c3f3592c1c717039b85eR164) `Annotate/Annotatef` and consider `Wrap/Wrapf`...

@develar this is one of several issues addressed in our fork. In this case, the forks are interoperable: one package can use pkg/errors and another package can use pingcap/errors. If...

Actually, thinking about this more, I have seen problems with the same interfaces defined in different packages. I would need to test to verify that you don't lose stack depth...

I have implemented solution 2 for GKE. You can choose between LVM or RAID. It assumes that you want to combine all the available disks together (which is not necessarily...

To be more generally useful you would probably want to do disk combining based on some node pool labeling scheme or other metadata available at startup. This solution also causes...

@nyurik sorry I missed your message. GCP improvements here are still in the alpha phase. I haven't seen errors from mdadm. We just updated the script for an incompatibility with...

Actually, I think WAI is a much better target to start with than Yesod specifically.