cloud-computing

sealos 版本：4.0
OS版本：centos 7.9/ubuntu 20.04/rocky linux 8.6
错误：

• host 拼写错误：
  导致node安装的时候无法访问sealos.hub，然后去访问GCR，没挂梯子的话安装失败
  临时解决方案：修改/etc/hosts，将错误的拼写改掉，就可继续
• registry 无法挂载错误：
  在master01上挂载的registry 目录挂载不上，导致kube全家桶镜像装载不进去
  临时解决方案：在master01手工执行/var/lib/sealos/data/default/rootfs/scripts/init-registry.sh 5000 ~/registry/
• bash 执行错误：
  2022-07-08 10:38:02 [INF

What problem are you facing?

🚨🚨 Feature Request

• A new implementation (Improvement, Extension)

Is your feature request related to a problem?

Currently, if a user tries to access an index that is larger than the dataset length or tensor length, an internal error is thrown which is not easy to understand.

Description of the possible solution

We can catch the error and throw a more descriptive e

Task description:
When there are files uncommit(i.e. git status is dirty), e.g.

diff --git a/README.md b/README.md
index c4b12c21..81cc751b 100644
--- a/README.md
+++ b/README.md
@@ -1,3 +1,4 @@
+
 # Karmada
 
 ![Karmada-logo](docs/images/Karmada-logo-horizontal-color.png)

While building

Some of our log messages start with a capital letter and some don't.
We should ensure the messages are consistent and use a single style.

See example to inconsistency in cloudquery/cloudquery#1059:

(1) Add docstrings to methods
(2) Covert .format() methods to f strings for readability
(3) Make sure we are using Python 3.8 throughout
(4) zip extract_all() in ingest_flights.py can be simplified with a Path parameter

When you use Crane, you may have some questions.
Many questions are in common.
We will select some questions for the FAQ page on the docs web.
If the item is checked, that means that question is added to the FAQ page.
Keep docs up to date as possible.

Install

• CRD conflict - v1beta1.custom.metrics.k8s.io

helm install crane -n crane-s

Is your feature request related to a problem? Please describe.
The possibility to disable an incoming peering with liqoctl.

Describe the solution you'd like
A simple liqoctl subcommand to disable the incoming peering for this cluster, to stop the resource sharing and remove the pod scheduled by the remote cluster on the local one.