scale

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

tidb> show create table placement_rules\G
*************************** 1. row ***************************
       Table: PLACEMENT_RULES
Create Table: CREATE TABLE `PLACEMENT_RULES` (
  `POLICY_ID` bigint(64) NOT NULL,
  `CATALOG_NAME` varchar(512) NOT NULL

/area API
/kind good-first-issue

Describe the feature

For flagged fields like kubernetes.podspec-fieldref the validation should include the name of the feature flag to toggle in the error message it surfaces. The validation logic is roughly here: https://github.com/knative/serving/blob/644798277d9fe6715e4f638281141356df46d7e1/pkg/apis/serving/k8s_validation.go#L246

• oceanbase/oceanbase#486
• oceanbase/oceanbase#483
• oceanbase/oceanbase#482
• oceanbase/oceanbase#481
• oceanbase/oceanbase#480
• oceanbase/oceanbase#477
• oceanbase/oceanbase#476
• https://github.com/oceanbas

Describe the bug

flytectl register files command doesn't fail without --countinueOnError. It should fail with exit code 0.

Expected behavior

• Flytectl register should fail if there is an error
• Flytectl register should not fail if the user passes the --countinueOnError

Additional context to reproduce

No response

Screenshots

No response

Are

Is your feature request related to a problem? Please describe.
I would like to know how Brighter reacts if it receives messages from other systems.

Describe the solution you'd like
Would like to know if you can rely on default behavior or if any additional message headers are needed

Is your feature request related to a problem? Please describe.

Updating escalator config currently requires a pod restart. We should update escalator to automatically read new config upon changing on disk.

Describe the solution you'd like

Check for changes in nodegroup config before each run. If safe to do so, run with the new config.

*Describe alternatives you've considered