xixi
### What problem does this PR solve? In https://github.com/chaos-mesh/chaos-mesh/pull/2918, we bring each background process an uid to avoid reusing pid. However, in view of the compatibility of API, we cannot...
## chaosctl v2.2.0 - [x] #2950 - [x] #3056 - [x] #2992 - [ ] detailed documents
## Bug Report When API add some new fields that cannot be resolved automatically by gqlgen, we may miss the implementation of resolvers, which may cause ctrl server panic when...
## Feature Request - [x] server-side HTTPChaos #1858 - [ ] client-side HTTPChaos - [x] implementation #2555 - [x] #2971 - [ ] new options to differentiate client-side from server...
 As the picture.
close #360
**What feature you'd like to add:** Add no-stripe-log option, when it's enabled, secrets like `secret-key` or `session-token` won't be stripped in logs. **Why is this feature needed:** For debugging.
In latest master branch, the [secrets](https://github.com/juicedata/juicefs-csi-driver/blob/4084f3051a58dd409eb253fd9464b762e3b21891/pkg/juicefs/mount/builder/secret.go#L26) created by csi-node-plugin don't contain `session-token`, which results in session-token missing when formatting in the mount pod.
The result of current `make check` depends on the version of go toolchain. So we should add dev image to ensure reproduceable `make check` refer to [chaos mesh](https://github.com/chaos-mesh/chaos-mesh/tree/master/images/dev-env).
Analyzing fuzz-bugs manually is boring and ineffective, we need some tools to find the minimally reproducible SQL automatically. For example, we find the following tow queries behave differently in TiDB:...