Nace Sc

I found that those params maybe refers to the ARAP(A.K.A As-Rigid-As-Possible Shape Manipulation) , and the source paper is [here](https://igl.ethz.ch/projects/ARAP/arap_web.pdf) .

Currently no , generation is still the key idea for ezorm v2 , but we can accept [some generic helpers](https://github.com/ezbuy/ezorm/blob/main/v2/pkg/orm/orm.go) as the side branch.

I am OK with the PR , but the in-memory unarchive will raise the latency , IDK if it will cause the abuse .

I prefer to not accept this PR , since we already have internal-cache option and always-regenerate-chart-index option on the other hand , this kind of feature seems duplicate . What...

We just keep the compatibility in theory , if you have some unexpected behavior just provide your user-case . CM is stable itself but it depends on some 3rd storage...

hi @gevalo1 , what about your action actually looks like ? The error message shows that your blob type is not correct , I assume that your chart package is...

And also , could you add some testing code to prove the feature is worked as expected ?

I'll look at this , it seems that most of the CPU or latency are reported by `gopkg.in/yaml/[email protected]` . Our `v0.16.0` release takes the bumping in at #692 , and...

Hi @zmaxyan , I try to reproduce this use our HEAD via our [loadtesting script](https://github.com/helm/chartmuseum/blob/main/loadtesting/locustfile.py) and my Mac(local storage), but I do not see the lots of latency dopped as...

PVC can be various storage provision , and the storage throughout differs from the [providers](https://github.com/chartmuseum/storage) . Did you run it on AKS and use s3 as backend , or just...