Jakub Kuczys
Jakub Kuczys
This is still relevant but I guess should be marked as an improvement same as the issue on longhorn side: https://github.com/longhorn/longhorn/issues/9243
The explanation in https://github.com/harvester/harvester/issues/6267#issuecomment-2399134703 still applies.
The explanation in https://github.com/harvester/harvester/issues/6267#issuecomment-2399134703 still applies.
The explanation in [#6267 (comment)](https://github.com/harvester/harvester/issues/6267#issuecomment-2399134703) still applies.
> Since we did not support the zstd type on Longhorn v1, should we move this to an enhancement instead of a bug? FYI, the issue on longhorn's side is...
One could argue that, since this is marked as useful for development, maybe we should auto-enable it as part of the `--dev` flag, but I think that it would be...
It is currently unclear what Discord will do with this - this feature went through 3 different API implementations, I believe that the feature is presently in A/B testing in...
I don't really know how I would have to approach writing this if I'm being honest and I don't currently have time to dedicate to this. Maybe one day if...
It seems that there's an open PR for this. The best way to move this forward would be for an interested contributor to make a code review of it and...
@ichard26 looks like I might have copied something wrongly when I was making this PR. I updated the reproduction (**Input**) in PR description. And yes, this only happens on master,...