Olivier Pilotte

Same thing: aur/tusk 0.23.0-0

Ok, I understand. In this case, is there any way to provide a SSL certificate to the descheduler?

Actually, it's not really a duplicate. I'm trying to follow the documentation and it doesn't work. It's not an Unauthorized issue, it's a Missing credentials issue.

There's an extra character in the package name `ß`. Remove it.

Even after removing the extra character, the bit server refuses to start. ``` [4/4] Building fresh packages... success Installed "@teambit/[email protected]" with binaries: - bbit Done in 11.47s. + bit init...

Made some progress. In `scope.jsonc`, there seems to be a typo: `teambit.bit/scope` is wrong, should be `teambit/scope` ``` { "teambit/scope": { "description": "this is a simple demo scope for Harmony."...

Yeah I'm trying to run it on Kubernetes. It starts but after some time it crashes with no logs / cues on what's going on.

These are the full logs for the container: ``` + bbit init --bare - running command init [path]... successfully initialized an empty bare bit scope. + bbit start -v --log...