You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To be honest, I didn't try this, just something that came to my mind when having a short look at the sources.
So if this is not an issue actually, just close this.
But as far as the man page of zstd says, if you use --long with a value lager than 27 on compression, you also have to specify it on decompression.
But following the current logic, if you create a cache on a system with new zstd where --long is supported and then try to restore the cache on a system with old zstd where --long is not supported, the decompression will probably fail.
So I think a separate file name for zstd with --long is necessary.
The text was updated successfully, but these errors were encountered:
To be honest, I didn't try this, just something that came to my mind when having a short look at the sources.
So if this is not an issue actually, just close this.
But as far as the man page of
zstd
says, if you use--long
with a value lager than27
on compression, you also have to specify it on decompression.But following the current logic, if you create a cache on a system with new
zstd
where--long
is supported and then try to restore the cache on a system with oldzstd
where--long
is not supported, the decompression will probably fail.So I think a separate file name for
zstd
with--long
is necessary.The text was updated successfully, but these errors were encountered: