John T. Wodder II

@yarikoptic Should a version be set in changelogs generated by scriv, and, if so, how? The current release workflow only runs on pushes to `maint`, which I believe means that...

PR: https://github.com/datalad/datalad/pull/7009

@gaborbernat Ticket created: https://bugs.python.org/issue45264

@xd009642 Version 0.19.1 works.

@Phantsure I don't think that makes a difference. Just having exact file hashes in all of the recommended workflows isn't enough to explain *why* they should be there.

@Phantsure I'm suggesting they might not be familiar with the "When a cache hit occurs, cache wouldn't be updated" aspect of caching, yes.

@Phantsure Yes.

I've found the answer to the first question already: an invalid zarr will not always raise an error immediately upon opening. For example, if a chunk file is malformed, this...

@yarikoptic From the traceback, it looks like some sort of conflict between pytest and an improperly-implemented pytest assertion rewriting hook; does this package have any of the latter?

@yarikoptic Custom assertion rewriters are defined via [`pytest_assertrepr_compare`](https://docs.pytest.org/en/7.1.x/how-to/assert.html#defining-your-own-explanation-for-failed-assertions), but that doesn't seem to be present in the repo either.