Alexander Clausen

> Yes! This looks great and I would probably use it myself. Thanks for putting together such a nice little demo. Great to hear! I'll work on a minimal PR...

Thank you for the discussion and reviews! To pull the discussion back here, from the closed PR(s): ([#58](https://github.com/LDeakin/zarrs/pull/58#issuecomment-2319554719)): > Yep, that could probably work. The standard encode/decode methods of codecs...

> Did a bit more digging; it seems like this bug was introduced when the utility function `run_sync` was rewritten to no longer use `nest_asyncio`. This function was moved from...

Btw. this also concerns the LiberTEM-live repo, but there it is much easier because of the lower number of contributors. @matbryan52 what do you think about this? Your opinion is...

> Absolutely, I've always assumed this would happen one day with the push to put things into `libertem.common` where possible. Thanks for the reply! @uellue I'll assign the issue to...

Full error message: ``` Traceback (most recent call last): File "/home/runner/work/LiberTEM/LiberTEM/scripts/zenodo_upload", line 399, in main r = update_deposition(deposition_id=deposition_id, data=make_data()) File "/home/runner/work/LiberTEM/LiberTEM/scripts/zenodo_upload", line 150, in update_deposition raise ZenodoException(prettystring(r)) ZenodoException: Status code:...

> @sk1p sorry to bother, but what were the steps for a point release again? Sth about setting the version by hand? Yup, either setting the version to 0.14.1.dev0 by...

> Think we're done with the point release ? Conda release is good, and we haven't seen any fires that I'm aware of Thx! :+1:

/azp run libertem.libertem-data