InLAnn

Results 10 comments of InLAnn

It seems like the repository `https://kubernetes-charts.storage.googleapis.com` in the `helm/requirements.yaml` should be replaced with `https://charts.helm.sh/stable`: ```bash mac@master:~/Work/werft/helm$ helm repo add werft_test https://kubernetes-charts.storage.googleapis.com Error: repo "https://kubernetes-charts.storage.googleapis.com" is no longer available; try "https://charts.helm.sh/stable"...

> To use werft with GitHub you'll need a GitHub app. To create the app, please [follow the steps here](https://developer.repositories.github.com/apps/building-github-apps/creating-a-github-app/). The link of `creating-a-github-app` has been moved to `https://docs.github.com/en/enterprise-cloud@latest/developers/apps/building-github-apps/creating-a-github-app` BTW,...

Another question: The apiVersion `rbac.authorization.k8s.io/v1beta1` in the [werft/helm/templates/serviceaccount.yaml](https://github.com/csweichel/werft/blob/main/helm/templates/serviceaccount.yaml) has beed [deprecated in Kubernetes v1.22](https://kubernetes.io/docs/reference/using-api/deprecation-guide/#rbac-resources-v122). It's `rbac.authorization.k8s.io/v1` for now.

You need to check if there is any errors in your backend console since your titlebar is missing and your frontend windows does not work correctly.

BTW, does the MLX engine currently only support deepseek distillation models?

> > BTW, does the MLX engine currently only support deepseek distillation models? > > "deepseek-v3": { "layers": 61, "repo": { "MLXDynamicShardInferenceEngine": "mlx-community/DeepSeek-V3-4bit", }, }, "deepseek-v3-3bit": { "layers": 61, "repo":...

> It looks like `wails doctor` does detect them correctly and shows you the version. It looks like there's an environmental issue where `pkg-config` doesn't detect them? > > ```...

Hmmmm, you mean the dependencies list is generated based on the detection results and differences, right? I thought it was a fixed list, but it actually shows different Status fields...

In a new Fedora container, when running wails doctor, the status of GCC is shown as "installed," but when executing wails build, it throws an error saying GCC is missing....

> Well the right package is installed. The PATH in the container might not have the gcc bin dir in it. `locate gcc` or `which gcc` and check against `echo...