I think this one may be related to the issue with --keep-time and --retention-policy throwing not-that-user friendly errors when combined. They may be the same issue.
Not that I know of. I haven’t had the opportunity to try to replicate as I just saw it here on the forum. Maybe skip it and deal with it if it turns out to be a problem?
I think I can get Never mind, it’s a bit more tricky. The
U in with like 2 lines of code just translating it to
0s and before running the retention policy method since it’s just semantics.
K is very cool, but I also fear it may be quite a bit more work to implement. If we’re just aiming to ship quicker so we can get to next experimental release sooner, then it might not be terrible to just ship it as is once we handled the showstoppers