Ryan Abernathey

Thanks for this great action. I just hit this issue. It seems like it is impossible to provide a working `details_url`, due to the github API problem described above. Shouldn't...

Thanks for the reply! > From GitHub staff "We don’t support showing a details_url for check runs created with the Actions GITHUB_TOKEN." This is good advice. I'm going to see...

Just noting that Xarray has some magic that allows it to pickle h5py objects. This is discussed in https://github.com/pydata/xarray/issues/4242. We have considered trying to break this functionality out into a...

One issue (noted in https://github.com/zarr-developers/community/issues/37) is that many of the existing cloud-based Zarr data is optimized for backend analytics and consequently has chunk sizes of ~100 MB. This is probably...

> It looks like pulling the full global domain for a single time step will mean requesting 100 chunks that are ~40MB each. This is one reason why we would...

> In order to work with existing Zarr stores with a large block size, you could also take a more server-side approach Big 👍 to this idea. Dynamic rechunking is...

Xpublish has extra endpoints for convenience, but clients don't have to use them. To the client, the data are indistinguishable from static zarr files served over http.

I am in favor of this change.

It is much easier to review small, self-contained PRs than huge ones with many separate changes. So we should definitely encourage this. I personally don't think it's very important to...

> My problem with xmitgcm was that it didn't work on file systems with ulimit set. It would be great if you could report this via an xmitgcm issue. (It's...